Macworld UK is reporting that Microsoft Office 2008 for Mac saw record sales since its release, becoming the best selling version ever. Of particular interest, however, is that Microsoft has announced the next version of Office will return Visual Basic for Applications (VBA) to the Mac platform.

You may recall that one of the big brouhahas connected with Office 2008 was the elimination of VBA, which was present in Office 2004 and earlier versions; Microsoft suggested that users rearchitect their macros and automation with AppleScript. While it's generally a good thing for third-party applications to support AppleScript thoroughly, in this case it created a lot of problems for cross-platform users since the Windows version of Office depends on VBA for macros. While it is possible to duplicate some (though not all) VBA functionality with AppleScript, cross-platform macros were completely broken, leaving some users, especially in corporate environments, unwilling to upgrade from Office 2004. In this light, it is good news that VBA will return, though no timeline is yet available.

In addition to the roadmap announcements, today Microsoft is also releasing Service Pack 1 for Office for Mac 2008 with a host of improvements, including improved compatibility with Windows versions and better printing support. It should available for download at noon PDT from Microsoft or via Auto Update in Office. Full change list in the continuation of this post.

Update: Mac BU developer Erik Schwiebert has a post up on the revitalization of VBA; he originally discussed the decision not to implement it for Office 2008 here.

As someone who spent months hand-crafting Visual Basic scripts in Microsoft Office, only to have Microsoft pull the rug out from under me with the release of Office 2008 (they abandoned VB support for the Mac. Grrr.), I'm very grateful to MacTech magazine and longtime AppleScript guru Paul Berkowitz.

MacTech has re-released Paul's 150-page guide for making the transition from VBA to AppleScript (originally printed in the April 2007 issue of the magazine, and also available in modified form on the Microsoft Mac BU site). It's highly detailed, with step-by-step instructions. It looks like I know what I'll be reading next week (and if I run into trouble I can always bug Cory for help).

You can download the guide as a PDF for $9.95US, or get the PDF plus a hardcover version for $19.95US. Both options include a free subscription to MacTech magazine, which is a great bonus for anyone who likes to dig into the underside of Mac OS X. If your wallet is a bit light, you can read the entire thing online for free.

We've mentioned before Microsoft's controversial decision to end support for Visual Basic (VBA) scripting in the forthcoming Office 2008 and replace it with AppleScript. While normally moving to an Apple standard technology over a closed Microsoft solution is a good thing, this move will have major repercussions with respect to cross-platform compatibility. Once this is done many scripts and macros written for the Windows versions of MS Office will no longer work on the Mac version. There is a work-around, rewriting the macros and scripts in AppleScript, though that will take some doing. Fortunately, MacTech magazine has produced a VBA to Applescript Transition Guide to help with the process. Originally the Guide was only included with the April issue of MacTech Magazine, but they have now seen the light and are offering it free on their website. You can still purchase a PDF or paper copy as well. Check it out over at MacTech.

[via The Apple Blog]

MacWindows.com recently polled readers on their willingness to upgrade to Office 2008 for Mac, which will not include Visual Basic for macros and automation (as noted on this MacBU developer blog). Several readers said they won't upgrade to 2008 because they depend on VB cross-platform support.

Where I work, we have an intricate system in place that manages and analyzes loads of data on a daily basis-a system that is dependent on homemade VB scripts. So, there's no way we're upgrading. Good job, Microsoft.

By the way, if you're left in a jam by this, check out MacTech Magazine's guide for moving from VB to Applescript, which will be available soon.