Voters 1
1
Allow comparing create and modified dates to each other in advanced search
- Open
- Subscribe
 |
D H |
I need to find files that have been modified, or have odd create/modified dates due to file copies or restores that overwrote the create date.
So, scenario #1 is the simple one of last modified date > create date to identify modified files.
For scenario #2 I have files where the modified date is earlier than the create date, like;
Create Date: June 1, 2022
Modified Date: October 15, 2015
which I'd also like to search for.
So, greater, less and equal search options would be better than something that assumes a modified file is one where the modified date is after, or not equal to, it's create date.
Activity Newest / Oldest
Team TreeSize
Status changed to: Open
Team TreeSize
Status changed to: Under review
Team TreeSize
To pick up your example: If you copy a file last modified on Oct 15, 2015 to another drive on June 1 2022, then this file is first created there on June 1, 2002. And since it was not modified, only copied, the last modified date stays as it was on the source drive. So the time stamps are valid and expected.
May I ask why you are searching for those files and what you intend to do with the search results?
D H
Well in scenario #1 I'm just trying to find files that have been modified. I don't know or care when they were modified, so searching by date ranges or days offsets doesn't really help. I don't know of any other "modified flag" in the file system metadata, so the best proxy is a comparison to create date. It may not be ideal if create date isn't meant to be used as the document create date, but the alternative would be a lot harder, accessing document-specific metadata like EXIF data or Office doc properties.
answers.microsoft.com/en-us/windows/forum/all/file-explorer-and-date-createdmodified-change-when/e6ad833e-a134-4da8-a9e0-815c92eeecfa
Examples would be a PDF document I saved then edited with Adobe Acrobat or a photo I edited in-place.
My point in mentioning scenario #2 was just a way of trying to say "please don't just add a derived flag that is based on a simple test of 'modified date not equal to create date', or 'modified date greater than create date'" because neither of those would always catch the files one might be looking for.
Team TreeSize
OK, I understand, you mean: All files modified at least once after they were created, and their creation does not count as modification.