Hi George,

I think there is a pattern, it is this:

If x=seconds (to the millisecond) reported by getFileTime() then seconds reported by adir and ftime is always ceiling(x) + mod(ceiling(x),2) that is, always returns the next highest even integer) while wsh reports floor(x). Thus, the only place they all agree is when the seconds is and even integer which is always the case on a FAT drive since that is the highest resolution afforded by that file system.

Anyway, thanks for confirming that I wasn't just seeing things.


>Second, I finally see what you're seeing. I can accept that ADIR() and FTIME() would always round up to the next whole second (as if the CIELING() function was in use). What isn't acceptable are those instances where it rounds up more than 1 second. Unfortunately, these seem to be rather sporadic and show no pattern whatsoever. I've see it occur with values greater than .500 and less than that. Further, I've seen it with odd and even values above and below that value. You might want to submit a bug report. I don't see a KB article in the October 2001 edition of the MSDN Library covering this, but there may be one on-line.