Windows native and system copy

[Kenneth Brody]

Quoting GCC Consulting (Tue, 22 Mar 2005 09:57:00 -0500):
[...]
> > 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.

It could be.  ;-)

> Now, as I said, if the batch file is run from the command prompt, it
> works perfectly.

Define "works perfectly".

Remember, it "works perfectly" when filePro calls the batch file as
well, as long as you tell filePro to wait a short while before trying
to access the file.  Hae you tried accessing the file _immediately_
upon returning from the batch file?  (And I mean _immediately_, just as
filePro would do without the sleep.)

> 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?

When task manager starts what program?  filePro?  The batch file to do
the copy?  Something else?

--
KenBrody at BestWeb dot net        spamtrap: <g8ymh8uf001 at sneakemail.com>
http://www.hvcomputer.com
http://www.fileProPlus.com