Hi all -

Here's what appears to be a strange behavior we've noticed and recreated using FoxPro, Visual Studio .NET and COMMMAND.COM. Using the technology of your choice create code that will delete a destination file in some folder (networked or local), followed by copying of a source file to that same destination file. Once you run this more than once you are essentially:

1. Deleting the destination file.
2. (re)Creating the destination file.

If you look at the properties for the destination file after the 2 - n running of the above code you will find the Created Datetime will reflect the FIRST running of the code (even though the Accessed Datetime always and correctly reflects the last running of the code).

It appears, however, if you wait for some period of time between the delete and the copy (usually a minute or two is sufficient) the destination file's Created Datetime will then correctly reflect the most recent copy datetime.

Anyone understand why the Created Datetime is not bumped up to reflect the Datetime the destination file was created? Feeling to me like Windows is holding off on some housekeeping for the deleted file and then ends up not doing it once the new file is created?

Thanks.