>>Any time/date stamping is a function of the OS, not FoxPro. When VFP sends an update to a file, it's the OS's responsibility to properly modify the last access and last modification date and times.
>
>
>Thanks George.
>
>So, VFP never looks at the header of a file to find out if it has been modified either ? _Everything_ is up to the OS ?

It looks - else how would it know whether it has to recompile (not in runtime, of course). Besides, it uses some kind of timestamp in .pjx, frx, scx and .vcx files, to know if something's obsolete and needs recompiling.

You can also use the FDate() and FTime() functions, but - all of the things I've mentioned here actually use the date and time of the file which you see when you look into a directory listing (I still call it directory, because there's no FOL command in DOS7, only DIR). And this time gets written by the OS when the file is closed (attention here! _when_it_is_closed_). So any problems you may have may come from either faulty OS which doesn't refresh the dates properly, or you have a situation when the file in question has not been closed since the last change, and therefore still bears the date of last close-after-change.