File timestamp changed but file is not closed!

[LaRetta]

Help! I may be panicking needlessly; God, I hope so. I thought a file didn't update its date/timestamp (when being served) until the file was closed. I just looked at our file (through Admin). Both services are running (normal). Database status is normal on all. But the date/timestamp says 45 minutes ago and we have NOT stopped serves or closed the databases!

I feel my fingers going weak. Please tell I'm wrong and a served file sometimes updates this date/timestamp even when not closed. Please tell me that. It performed a backup at 4pm. The last User signed off at 5:11. The timestamp is 5:15.

L

Edited March 10, 2007 by Guest
Fixed scrambed subject

[LaRetta]

:blush2: OMG, I was so perplexed that I turned off the services before I closed the databases.

The entire desktop is Notepad at 88 pt font in red saying, "close databases THEN stop services." Geez ... and I get on Users for not reading messages. I'm usually VERY careful!

I noticed it wrote 6:03 timestamp also (it backed up again). Closing services was a bit slow (6:28pm) but I stayed patient. Have I just trashed the file? Luckily it just backed up. I guess I've just never noticed that timestamp changing because I've always pay attention to the timestamp when I close it; not before.

I hope stopping the services closes the databases properly. Do I sound a bit skittish about my served solution? Yep.

L

Edited March 10, 2007 by Guest

[Steven H. Blackwell]

I hope stopping the services closes the databases properly.

There is no guarantee that this will occur. So, that's why the official recommendation from the FMI SE's is to close the files via the SAT Tool and then stop the FMS service as well.

Steven