[AccessD] Shelling to dos

That is perfect.  I need it to just go do it's thing. 


John W. Colby
www.ColbyConsulting.com 


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of MartyConnelly
Sent: Saturday, February 04, 2006 12:49 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Shelling to dos

The Shell process flails around on its own, If you need to know when the
process ends
 
http://vbnet.mvps.org/code/faq/getexitcprocess.htm

 get a return code if it sends one from ShellEx Shamil had a couple of posts
on this about 2 or 3 months back

If the Shell function successfully executes the named file, it returns the
task ID of the started program. The task ID is a unique number that
identifies the running program. If the Shell function can't start the named
program, an error occurs.

Note   The Shell function runs other programs asynchronously. This means 
that a program started with Shell might not finish executing before the
statements following the Shell function are executed.





John Colby wrote:

>Does a shell to dos run in its own thread, i.e. will the shell command
>return instantly, leaving the Dos process running?
>
>I need to Xcopy a directory from here to there.  Rather than doing that
from
>inside of Access and tying up my program, I thought I would run a batch
file
>that does an Xcopy with a ton of switches that copies subdirs, sets the
>archive bit etc.  This only really helps if the shell returns once it gets
>the xcopy running, but Xcopy must continue to run after the shell command
>returns.
>
>John W. Colby
>www.ColbyConsulting.com 
>
>
>  
>

-- 
Marty Connelly
Victoria, B.C.
Canada



-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com