berkowit28 said:The reason MacBU has had to abandon VBA is that the Mac compiler won't work on Intel Macs. And Microsoft has already announced that VBA is being deprecated on Windows (it will go on working for a few years, then will end). So there's no point devoting enormous efforts to making a new compiler only for it all to go away shortly afterwards. There is some reason to believe that eventually VB.NET will work on the Mac as it does on Windows, as a cross-platform solution. Until then, VBA macros need to be translated to AppleScript. There can be no better signal that MacBU is committeed to the Mac than to see the huge investment they have made in AppleScript. Office's AppleScript is already working as of Office 2004, and it mirrors the VBA model identically: macros can be translated to AppleScript _now_, and will then "just work" in the next version of Office too.
I was actually wondering about just this, if MS is going to a new open standard for documents, and apple also does in their own products, wont word be just another nice frontend that performs the same functions as most other apps. Most people, me included, use Office for mac for compatibility, if thats out of the way I wont use office anymore. Will the new open format (ODF I believe) use its own scripting language, or what?