Half the reason I haven't been on the site much is that I'm getting tired of all the cross-platform issues with VBA. For example, I can't test most of the KBs at home because they rely either on VB6 or ActiveX.

So now we're going to lose VBA from Mac Office. Might be the first time that MS has removed a feature. I'm sure they'll call it a bug fix. And they're trying to convince us to use AppleScript instead. What a joke. AppleScript has a lot of good uses, but dealing with scientific data in a spreadsheet is not one of them. Not to mention the absolute lack of decent documentation for AppleScript. At the moment you can also allegedly use RealBASIC within Excel for Mac - wonder if that's going to stay or not. Will they ever port VB.NET or VB 2005 or whatever they're calling it these days?

I'm starting to think like shades. Write up the code in a third party compiler, generate a stand alone executable that dumps results into Excel or whatever other spreadsheet I have by then. Without a scripting language built into Office that runs on both platforms, I no longer have a fundamental reason to stick with Office.