I've just noticed that the timestamps on my applications DAT and DB files are an hour in the future of the time settings on both my server and my workstation.  Any idea why this might be and what I should do about it?

Which OS?  If one of my LAN workstations has a bad setting, would that stamp it?  I always thought it was the server's time, which is currently correct.  As for how long, I don't know, sorry, just noticed it today when cleaning out my Reports folder and noticing some funky report names.

Well this is the damndest thing.  I've double-checked the server time setting (even reset it to a minute ahead and hit apply).  The I went into Sesame, opened a form and hit Alt+F5 in a field.  The correct time appears.  I did not save the change.  But other users have been using the same DB, and right now, at 10:25 AM, the time stamp on MIARA.DB is 11:03 AM.

None of my applications use time-stamping so I'm not terribly worried about it, but it's very puzzling.  I think that, as soon as I can, I'll shut everything down, reboot the server, check the time setting, and start Sesame up again, see if that helps.  Probably not before next week, though (I need to do it at a time when no one else is using the network.)

Thanks for your help, Mark!

It's because of "Automatically adjust for Daylight Savings Time".  On workstations (and the server) when this is checked, it flips the display of the stamp one hour ahead.  Turn it off and refresh and ta-dah, the time stamp is correct.  Microsoft can bite me.