Hello,
You have several options (I would try them in this order):
1. If you have selected the option
Don't wait for files to be available on the GUI (watchDirectoryStart), please
deselect it. This option, when selected, corresponds to the
/C command line option.
If you
don't select this option, WD will try to open the new/changed files before calling you .bat file. If the program that is writing to the file uses normal Windows file locking (for example, MS Word does this), then WD will start your .bat when the other application closes the file.
If you
do select this option, WD will call your .bat file as soon as a new/changed file is detected, even when that file is still in use.
2. If '1' does not help it probably means the program writing to the file does not use standard file locking mechanisms. We have 2 free programs (
http://www.gdps.dk/products/freeware.shtml) that may be of help.
WaitForFile this program will wait until it can gain exclusive access to a file. It uses an algorithm very much like WD, so perhaps it won't be perfect for this situation.
I am very confident that the other program,
WaitFileComplete, will do the trick. This program monitors the size of a file and waits until the size 'stabalizes'.
Hope this helps,
Gert