I am using a macro for the weekly backup. It is moderately complex but essentially selects all files and copies them with some options.
Intermittently, the macro fails with an error that shouldn't be possible. It thinks that there are no files selected so the attempted F5 copy command fails because it is "disabled". I have banged my head against the wall many times to understand this rare bug -- to no avail
I know it is kind of crazy even discussing this bug with you lot, but has anybody seen such a weird macro failure? Have you noticed a pattern perhaps?
I have occasionally observed the "CopyTo" function failing to recognize a newer file (not necessarily all newer files), and not specifically related to macros (but often used in a macro with COMMAND 32793).
you mean it doesn't pick up new/modified files? In what scenario and what other options?
you can check the error log to see if there were any file access problems
It picks up most of the updated files, but sometimes misses one file. There are no errors. The "Overwrite if newer" option doesn't seem to see the the change, even though the detailed list clearly shows a newer file time in the source directory.
