>Hi George,
>
>These results look perfect for a FAT drive. Create time to the milisecond, write time with 2 second resolution. Try it on an NTFS drive and you'll see what I mean (I think). The adir and ftime results will always produce an even number of seconds and and the API results for last write time will be to the millisecond (ie, different from the FAT results below). IOW, adir and ftime do not make use of the increased NTFS resolution.
>
>-lc
Lauren,

Well here are the results (and I've run the program several times and they are consistent) that I get on my Win2K Pro SP2 (with NTFS)

pre-write: 01/07/02 09:03:41 AM
post-write: 01/07/02 09:03:41 AM
adir time: 09:03:42 && Expected
ftime() time: 09:03:42 AM && Expected
post-read: 01/07/02 09:03:41 AM && Expected
----------------------------------
API: GetFileTime() results
Create date: 01/07/02
Create time: 09:02:41.743 && Expected
Last access date: 01/07/02 
Last access time: 09:03:41.231 && Expected
Last write date: 01/07/02 
Last write time: 09:03:41.231 && Expected

The only difference that I see is that VFP is rounding up to the next second in each case.