No More VBA after Office 2007

[Billy Rogers]

I just read that Microsoft will no longer include VBA with the next version
office. They have just delivered office 2008 for Macs without it. They
want everyone to use VSTO.

This seems crazy to me. I've spent the last three years getting good at VBA
programming in Access, Excel and Outlook and now they are going to make that
effort and knowledge obsolete.

Plus I really think it will make Office development much slower. Right now
I can just hit Alt+F11 and modify code if something isn't working right. I
love the fact that it's so quick.
--
Billy Rogers

Dallas,TX

Currently Using SQL Server 2000, Office 2000 and Office 2003

http://thedataguru.blogspot.com/

 

[XP]

See also: http://www.macwindows.com/office2008.html

This sucks.

 

[Allen Browne]

I read some of those reports too, but the information is WRONG!

The next version of Access will still have VBA in it. Microsoft is not silly
enough to break almost every non-trivial Access database in existence.

Someone messed up with those reports.

 

[XP]

Thanks for your post. While it seems too fantastic, the articles are well
written and seem factual.

Thanks for dispelling this. But, to your knowledge, is VSTA/VSTO the
replacement for VBA?

If so, how long have we got to come up to speed? Is VSTA included in the
software like VBA or will we be forced to purchase it?

Are there any definitive articles from MS that discuss this?

 

[Tony Toews [MVP]]

I just read that Microsoft will no longer include VBA with the next version
office.

Where? What's the URL?
http://www.regdeveloper.co.uk/2008/01/14/office_mac_08_vba/

This is completely wrong. The next version of Access will have our
familiar VBA in it.

They have just delivered office 2008 for Macs without it. They
want everyone to use VSTO.

Yes, however the Mac group in Microsoft are *NOT* the Office group.
They also notified everybody of their decision back in 2006-08-08. Or
almost a year and a half ago.

This seems crazy to me. I've spent the last three years getting good at VBA
programming in Access, Excel and Outlook and now they are going to make that
effort and knowledge obsolete.

And I've spent, uhh, more than a decade.

Plus I really think it will make Office development much slower. Right now
I can just hit Alt+F11 and modify code if something isn't working right. I
love the fact that it's so quick.

Agreed. However I would assume that any such solution, AND THERE ARE
NO CURRENT PLANS FOR ANY TO MY KNOWLEDGE, would have an equally tight
integration.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Tony Toews [MVP]]

See also: http://www.macwindows.com/office2008.html
This sucks.

For users of Mac Office sure. But this is *not* relevant for Office

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Tony Toews [MVP]]

I just read that Microsoft will no longer include VBA with the next version
office.

For the official word see
VBA in Office 14
http://blogs.msdn.com/access/archive/2008/01/17/vba-in-office-14.aspx

For Excel see
Clarification on VBA Support
http://blogs.msdn.com/excel/archive/2008/01/16/clarification-on-vba-support.aspx

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/