C
Chromag
We're having a problem where users will be working on files and Word
will just STOP saving changes. A user will work for an hour updating
a document and will click the save button. After clicking save, they
get no error, everything looks fine, and they close the document. But
the hour worth of changes are not saved and the Modified Date doesn't
change. If the SAME user double clicks and opens the file they see
their changes but if someone else opens the file they get the old
version.
Sometimes if they just close all their open word documents the changes
will be flushed and the files will actually save. Any idea what could
be causing this problem? I'm frustrated to the point of calling
Microsoft Support but figured I would try here first.
This problem generally happens to a file created or modified by Word
2007 (saving in 2003 format), saved, and opened and modified by a Word
2003 user who is using the office converter plugin.
These files are generally stored on a Windows 2003 Server.
Any ideas what could be causing this problem? It's really becoming a
serious issue at this point. It all started around November 2009 -
never had the problem before.
will just STOP saving changes. A user will work for an hour updating
a document and will click the save button. After clicking save, they
get no error, everything looks fine, and they close the document. But
the hour worth of changes are not saved and the Modified Date doesn't
change. If the SAME user double clicks and opens the file they see
their changes but if someone else opens the file they get the old
version.
Sometimes if they just close all their open word documents the changes
will be flushed and the files will actually save. Any idea what could
be causing this problem? I'm frustrated to the point of calling
Microsoft Support but figured I would try here first.
This problem generally happens to a file created or modified by Word
2007 (saving in 2003 format), saved, and opened and modified by a Word
2003 user who is using the office converter plugin.
These files are generally stored on a Windows 2003 Server.
Any ideas what could be causing this problem? It's really becoming a
serious issue at this point. It all started around November 2009 -
never had the problem before.