A user recently reported a problem with one of my applications that has me really scratching my head. Here is what is going on:

Whenever the primary user adds records to a table, I have fields in the record that stores the date/time the record was added. Now, at the same time, the underlying OS should be updating the DOS date/time stamp for the actual file, but it's not! If I hadn't seen this with my own eyes, I wouldn't have believed something like this is possible. But trust me, it's happening!

The last record in the table is stamped with a date of 05/03/1999, and if I do an LUPDATE() on the file it reports 05/03/1999, but when you perform a DIR from a command prompt, the date is being reported as 04/30/1999.

The date stamp on the file is important to me because that's how my program logic determines whether a remote dial-in user should download the changed file. The program is comparing the last time they performed a download (stored in the registry), with the FDATE() of the remote file. I am not using LUPDATE() because it's not Y2k compliant in VFP 5.

OS used: Windows NT 4.0 SP 3 on server and clients

Anybody else ever observed behavior like this?

-Tim