I've found a strange situation where the directory field "Date Created" does not change after a copy/paste using Windows Explorer.
Here's the scenario:
1) Image files are written to a folder on the hard drive from an SD card.
2) "Date Modified" shows the time/date the photo was taken, as written by the camera. "Date Created" is the time/date the photos were copied from the SD card to the folder on the hard drive.
3) A file is opened from this folder into a photo editor and modified.
4) The modified image is written to a DIFFERENT folder.
5) On the new/modified image, "Date Modified" is still the original time/date the photo was taken. "Date Created" is now the time/date the new image file was written by the photo editor.
6) I now have two different image files in two different folders. One (A) is the original, the other (B) is a modified copy.
7) "Date Modified" on "A" and "B" are the same. "Date Created" on "A" and "B" is different.
8) The modified image is copied to the image in the original folder using Copy/Paste operation Windows Explorer. The "overwrite" warning clearly shows the file has changed in size. A "Yes" indication is given. The file copies.
9) The file in the original folder now shows the new size.
10) After I have performed the copy operation, I find the the "Date Created" field HAS NOT CHANGED (it still shows the time/date that was on "A", not "B"), yet the file size HAS changed indicating a copy of "B" content actually took place and overwrote "A".
11) I also notice the thumbnail image does not reflect the edited changes, it still shows the original file. However if you open the file for viewing, the changed image is there.
This is causing problems with my backup. The modified files are not getting backed up again as "changed", apparently because the "Date Created" field hasn't changed.
So, why doesn't "Date Created" changed after the copy/paste? Why is it keeping the value of the original file and not the one that overwrote it?
Is this an indexing issue? How can indexing be forced if that's the case? (I already tried hitting F5, nothing).
Is this a Windows 7 bug? If not, what's the logic for this? Makes no sense, and it's causing problems.