>Lauren,
>
>Nick N had the same question for me yesterday regarding the code (Winfiles) that I have in the download section. I think that my response to him may explain what you're seeing (the following is from the Platform SDK):

Hi George,

Yes, I found the same SDK docs yesterday when I was trying to track down the problem. However, I don't think it explains this behaviour. If writes have a resolution of 2 seconds, I would expect that the actual time stamped on the file to be accurate +-2 seconds. This would explain why datetime() called just after the file is written would differ from what ftime() and adir() report.

However, this doesn't explain why adir and ftime differ from the getFileTime API function. I would have thought that fTime() and aDir() and getFileTime() would get their information from the same place: the file attributes.

>"Not all file systems can record creation and last access time and not all file systems record them in the same manner. For example, on NT FAT, create time has a resolution of 10 milliseconds, write time has a resolution of 2 seconds, and access time has a resolution of 1 day (really, the access date). On NTFS, access time has a resolution of 1 hour. Therefore, the GetFileTime function may not return the same file time information set using the SetFileTime function. Furthermore, FAT records times on disk in local time. However, NTFS records times on disk in UTC. For more information, see File Times."