Since TCC/LE is provided as is without support, I thought I'd cross-post it here since the error also exists in full version of TCC. Here's a link to the post in the TCC/LE forum instead of creating additional entries.
Ok, so it is WAD.
But shouldn't this become settled?
Perhaps by letting the user choose whether to recurse all directories respectively appy the range only to files?
In fact I have very huge directories and want to give my users a kind of fileage-assessment.
Since moving an old file into a directory modifies the directory, it "w" timestamp is changed. 99.9% of my accesses do not care what the directory dates are, only files. The complimentary issue is even worse - let directory A and its subdirectory B be older than the date range of interest, but let B's subdirectory C contain a file in the selected range. It will not be reported!
Since the issue is raised relating to @FILESIZE, not @DIRECTORYSIZE, I would like to see the DESIGN changed - when a request is made for members of a directory hierarchy within a specific date range, ALL matching members should be included, even if there is a directory level in the path to the matching member which does not match. I would compare this to trying to locate all 25-year old soldiers in a batallion, and the report ignoring the 25-year olds in units whose commander is older or younger.
I use this thread relating to the release of 13.04.62. Is this change of behavior applicable to ALL commands which use both a date range and /S, so the "copy /s /[d] xxx\ yyy\" command will copy all files from the xxx hierarchy that are today's, even if some directory in the path between xxx\ and the file has NOT been modified today, e.g., if the only new file in the tree is "xxx\yyy\zzz\aaa\today.txt", today.txt will be copied?