Originally Posted by
nmenaker
I would caveat the excell and other msft office comment above with a +1 for compatibilty but with the caveat that the FONTS must be the same or similar class. I HAVE HAD translation errors when the font isn't present on one or the other system, and the system replaces it and then one can get border, magin and page errors.
This applies equally to file transfers between two Windows machines or two Macs. It's inherent in file sharing. If this sort of thing matters, you have to check it on each system. It may not be the same as it was on the system where the file came from, even if both use the same platform.
Originally Posted by
boberonicus
I am a Mac fanboy but I have to call foul on this one. The Office 2008 suite does not support Visual Basic, and thus any homemade macros that automate functions or process data won't work in 2008. This has been a keen source of frustration for me; seems like it's something Microsoft is doing just to prevent compatibility for power users and custom apps and keep the score a bit higher on the XP/Vista side.
Good point about VB, if that's an issue. I don't use it, so I didn't think of it. Thanks for pointing it out.