>>
>>Nope apparently not, since the format returns what maps to a VFP datetime data type, which only supports a resolution down to a second.
>>
>>As a side note, you might want to look at my Winfiles program in the download section. That does all the necessary conversions for you. You'd just have to add a millisecond property.
>
>Winfiles already on my disk :) Wish I knew this before reinventing the wheel :)

Cetin,

Just some additional info you may or may not be aware of. I just took a look at this, and part of what's written here is known and part is deduction from what I've seen.

What's known is that the last access date/time is meaningless in terms of the time portion. It'll always be midnight.

What's a deduction is that, apparently, the only place that milliseconds is used is the creation date/time. I've tested 3 different files. In each case the creation date time was down to the millisecond. The last write date time showed zero in terms of milliseconds for all three cases. I think it's a pretty remote possibility that all three would be zero if this wasn't the case. Further, according to the MSDN Library description of the GetFileTime() function, the creation date/time is accurate to within 10 millseconds, but on NTFS files systems the last write date/time is accurate to within 2 seconds. This seems to support my conclusion.