I run a VB5(SP3) application that reports differences between files on two drives based on the date/time of the file (as reported by the FileDateTime() function). The app allows the user to copy the newer file over to the other drive (implemented by using the FileCopy() command) in order to synchroinze the two sets of files.
This works fine under Windows 95. However, under Windows NT(SP3), when VB5's FileCopy() command copies a file to the other location, it modifies the time of the target file by adding one second to the new file's time. (Yes, it really does. I didn't believe it myself until I tested it.)
The source file remains unchanged.
This only occurs under Windows NT, and only when the target file in the FileCopy() function is removable media (A: or zip drive). This same scenario does not occur when synching two directories on the same hard drive. (I only have one hard drive, so I can't test whether this occurs between two different hard drives)
Has anybody ever heard of such a thing? Any ideas what's going on?