Whenever an Excel file is opened, even just for perusal, the timestamp
on the file is changed to the moment in which it was closed. This
throws a wrench into attempts to keep files synchronized between
computers. The file will appear to be "new" even though you may have
opened up an older revision of it. One may also open a file, change
some formatting for the purpose of screen capture (or printing) and
not save it because the changes aren't meant to be kept. The file
timestamp still changes.

Is there a workaround to this? From usenet, it appears to be an age-
old problem.

Thx.

If you close the file without changing it, the timestamp will go back to its
original value.
--
David Biddulph

"Paul" wrote in message
...
Whenever an Excel file is opened, even just for perusal, the timestamp
on the file is changed to the moment in which it was closed. This
throws a wrench into attempts to keep files synchronized between
computers. The file will appear to be "new" even though you may have
opened up an older revision of it. One may also open a file, change
some formatting for the purpose of screen capture (or printing) and
not save it because the changes aren't meant to be kept. The file
timestamp still changes.

Is there a workaround to this? From usenet, it appears to be an age-
old problem.

Thx.

Huh. OK. I won't be in a position to try it for 1.5 weeks, but it
would certainly make life simpler. Thanks!

On Apr 3, 11:54 am, "David Biddulph" <groups [at] biddulph.org.uk
wrote:
If you close the file without changing it, the timestamp will go back to its
original value.
--
David Biddulph

"Paul" wrote in message

...

Whenever an Excel file is opened, even just for perusal, the timestamp
on the file is changed to the moment in which it was closed. This
throws a wrench into attempts to keep files synchronized between
computers. The file will appear to be "new" even though you may have
opened up an older revision of it. One may also open a file, change
some formatting for the purpose of screen capture (or printing) and
not save it because the changes aren't meant to be kept. The file
timestamp still changes.

Is there a workaround to this? From usenet, it appears to be an age-
old problem.

Thx.