Hi Paul:
They should be.
The original issue was a bug in Win Excel 2007. The XML I/O module had a
bug in it that was writing dud code to the disk.
Because Win Excel 2007 used the same module for read and write, the problem
was never noticed until other things started trying to read the code.
The issue is fixed in a combination of Service Packs, from Microsoft for
Windows Xp/Vista/7 and Office 2007, from Microsoft for Office 2008,a nd from
Apple for OS 10.5.x and 10.6.x
Everyone gets a piece of this action
You need to make sure that the
latest service packs are applied at both ends.
"Re-opening" will not resolve it, as I am sure you are aware: you need to
"Save As" to write out a new file with the fixes in place.
The rest of the story is due to the fact that Microsoft Office 2008 is a
"lite" version that was rushed to market with a lot of bits missing.
Those bits are being replaced in Office for Mac 2010. So you will get a
much better experience in 2010.
In the meantime, people using Office professionally, are staying with
Office 2004.
As a former 'Softie, I am sure you're aware that nobody reading here has any
particular interest, one way or another, in whether or not you elect to use
some other software
I've never tried Numbers, I hear it does a good job for light-duty lists and
tables. You need to be able to live without macros, pivot tables, or
statistical analysis.
Cheers
As a former Microsoftie who's MIFFED that the groups can't maintain
cross-platform feature parity, I am even more frustrated that the file
corruption problems I've had in Mac Excel 08 ARE NOT resolved by reopening
with Win Excel 07.
Any OTHER suggestions? Or should I just dump my investment and start using
Numbers?
pt
--
This email is my business email -- Please do not email me about forum
matters unless you intend to pay!
John McGhie, Microsoft MVP (Word, Mac Word), Consultant Technical Writer,
McGhie Information Engineering Pty Ltd
Sydney, Australia. | Ph: +61 (0)4 1209 1410
+61 4 1209 1410, mailto:
[email protected]