|
Posted by Jim Michaels on 01/21/06 04:36
"Robin Haswell" <rob@digital-crocus.com> wrote in message
news:pan.2006.01.19.11.11.02.478252@digital-crocus.com...
> On Tue, 17 Jan 2006 23:56:47 +0000, Andy Hassall wrote:
>
>> On 17 Jan 2006 15:16:52 -0800, giloosh99@gmail.com wrote:
>>
>>>Exec, shell_exec, system, popen functions all run the process in the
>>>background.
>>
>> They don't normally, unless you do something fairly specific to get them
>> to.
>>
>>>how can i get it to run the process normally.
>>>my code looks like this:
>>><?
>>>exec("batch_file.bat");
>>>?>
>>>
>>>am i doing anything wrong?
>>
>> What's in batch_file.bat?
>
>
> I think your problem is MS Access is forking and running in the
> background, causing the BAT to exit.
do a start, run, cmd to get a cmd shell.
type in start /?
and look at your options. I think you can get the batch file to wait for
the process to finish before continuing.
and BTW, use .CMD instead of .BAT - it will give you these options. I can't
remember if .BAT files bring up command.com rather than cmd.exe. I think
they do. that is, if you are on an NT/2000/xp box. .CMD files will also
give you long filenames by default, and a bunch of extra commands and
switches. try doing a set /? and watch the fireworks. batch files can loop
and count and do calculations with CMD. (I'm sure this won't impress the
UNIX folk :-) )
>
> Open up a command window and run your bat file in it. How long before your
> BAT exits and goes back to the command prompt? If the answer is "before I
> close MS Access", then there's nothing you can do about it.
>
> -Rob
>
Navigation:
[Reply to this message]
|