H
hibitdat
Help!
We support a large number of Schools in our county (UK) and an
increasing number of them use Office 04 on the Mac. We are getting
almost daily complaints of Word literally loosing work, especially on
largish documents.
An example is a students project write-up. They work on the document as
needed, auto-save and backup are enabled and they save regularly. They
then close the document and Word, go and do something else on the Mac
(check emails, wacth a DVD etc) and then re-open Word and the document,
only to discover that some or all of the most recent changes are gone!
I have now had this happen myself on a few occasions using a Powerbook
that has a clean install of Tiger and Office 04 with all the updates to
both applied and nothing else - therefore we are rapidly reaching the
conclusion that Word 2004 for the Mac is fundamentally flawed and too
risky to recommend. Some customers have requested that we look into
viable open source alternatives.
Has anyone else seen this problem and better yet got a solution? I hope
Microsoft can fix this, and quick, before all confidence in the product
is lost.
We support a large number of Schools in our county (UK) and an
increasing number of them use Office 04 on the Mac. We are getting
almost daily complaints of Word literally loosing work, especially on
largish documents.
An example is a students project write-up. They work on the document as
needed, auto-save and backup are enabled and they save regularly. They
then close the document and Word, go and do something else on the Mac
(check emails, wacth a DVD etc) and then re-open Word and the document,
only to discover that some or all of the most recent changes are gone!
I have now had this happen myself on a few occasions using a Powerbook
that has a clean install of Tiger and Office 04 with all the updates to
both applied and nothing else - therefore we are rapidly reaching the
conclusion that Word 2004 for the Mac is fundamentally flawed and too
risky to recommend. Some customers have requested that we look into
viable open source alternatives.
Has anyone else seen this problem and better yet got a solution? I hope
Microsoft can fix this, and quick, before all confidence in the product
is lost.