David Glass wrote:
Unless Rb changes how it automates Office, I can't see how. Rb just
hooks into the VBA object library, if it is not present there is no
automation. This is one reason why on the Mac the Rb application has
to reside in the Office folder; so it can 'see' the VBA components.
This is bad on multiple levels.
Great. The Microsoft mailing list says that VBA won't be lost or damaged
when you open a PC file, but the VBA macros will not run, you cannot
edit them, and only limited support for Automator is being included. The
AppleScript support is spotty... at best. They (MacBU) claim the issue
was the shift from CW to Apple's programming tools. I don't get this.
They never updated VBA on the Mac, after matching VBA 5.0, did they?
So much for some project ideas I was playing with. As you know, I was
automating manuscript formatting and have a lot of automation when Susan
and I edit documents for clients. I use all sorts of macros to quickly
insert comments in student papers, too.
This annoys me. Maybe MS will be pressured to change this decision and
recreate a VBA interpreter on the Mac? Then again, I doubt it.
What other options would there be on the Mac? OpenOffice isn't native
and Neo crashes on my PB. I still don't know why. With OO, I get much
better performance on a PC. That sucks.
Thanks for any info, David. Susan and I even automated the manual
editing. Uhg.
- Scott
BTW: Know anyone in search of a color LaserJet 4550?
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
