This bug has been present for many years, but strangely I'm only now being called on it. The ForFilesIn macro command uses a Windows API call to gather a list of files matching your specification. Unfortunately that API function stores the filenames using the same options you have set in Explorer. So if you have "Hide file extensions for known file types" checked, file extensions aren't included with the listed files. When the macro facility then attempts to open each of those files, it fails to find them. No error messages are reported because
of course there
cannot be any errors since the files would not have been listed if they weren't there
.
You can get around the problem for now by ensuring that "Hide file extensions for known file types" is unchecked in Explorer. Next version will of course not make this mistake.
Thanks to Jonathan Orphal for his patience in helping track this one down.
