Windows native and system copy

[GCC Consulting]

> > Nancy has had some conversation with ken about this problem 
> and he has 
> > said that sleep isn't necessary.  However, Nancy and I feel 
> that, at 
> > least in a network/Windows environment, processing returns to the 
> > processing table before the new file has had a chance to close.  It 
> > will exist, but won't be closed and available for import or 
> whatever.
> >
> > By delaying processing those few seconds, it clears the problem.
> [...]
> 
> While I don't doubt that the sleep fixes the problem on your 
> system, I can tell you that this means that your system is 
> broken.  Unless you tell the O/S to run the copy in 
> background, the copy will be complete, the file will be 
> closed, and it will be available for anyone to access, prior 
> to it returning.  If control returns to filePro before the 
> file is actually copied, then either you explicitly told 
> Windows to run the copy in background (via "start"), or your 
> system is broken.
> 
Ken,

This run on Windows Server 2003 directly.  If it is broken, the Server 2003 is
broken.

Now, as I said, if the batch file is run from the command prompt, it works
perfectly.  It is when the task manager starts the program that the problem
occurs.  I am not using "start" to run the program.

Is it may be possible that the task manager routine is causing this problem?

Richard Kreiss
GCC Consulting