This is interesting. What significance does this have beyond the
omission of ActiveX? VBA 6 has been out for some time (I believe), so
are there plans in a future upgrade to Office 2004's VBA 5 to 6? Or
is a minor incompatibility as you suggest. Seems like MacXL should
have had this some time ago.
It's not going to be updated - I don't know how big a deal it would have
been to go to VBA6, but the demand was obviously not there. In any case,
VBA is a dead language walking, both on the Mac and Windows platforms.
Within a version or two it will be replaced on the Win side by a .Net
something.
Plans for the Mac side are seemingly more up in the air. MacBU is
pushing RealBasic, which is cross-platform compatible, but I'd rather
see a migration to something as close to WinOffice as possible.
You can always send your preferences to MacBU by using the Help/Send
Feedback... menu item in any Office app.
FWIW, I've written VBA5 equivalents of VBA6 functions, and store them in
an add-in, so I can create a reference to it in any projects with VBA6
calls. It works for me, and I'm starting to write an article on how the
macros I use for my website. The alternative I use commercially is
conditional compilation - using VBA6 calls for WinXL2000 and above, and
VBA5 for MacXL/WinXL97.
