Does the file-trigger script know the path of the copy-source folder? Then we can make the script better. But it can't be used when *moving* instead of *copying*.
In any case can't make this 100% reliable. And the code isn't easy to create. Need to manage multiple "file change" events. Possibly slow.
If possible, instead use a script (eg cmd, PowerShell or QM) that copies files and then launches a QM macro. Then don't need a file trigger + code to wait until all files completely copied.
In any case can't make this 100% reliable. And the code isn't easy to create. Need to manage multiple "file change" events. Possibly slow.
If possible, instead use a script (eg cmd, PowerShell or QM) that copies files and then launches a QM macro. Then don't need a file trigger + code to wait until all files completely copied.