J
Jim Evans
I have a task that requires the creation of a .bat File and then the
execution of that .bat file.
If I write a procedure that calls procedure 1 (to create the .bat file), can
I be certain that the file will be created and closed before I call
procedure 2 (to execute the .bat file)?
Currently, I use 2 buttons on a form to achieve this. After entering the
data into the form to mark certain records in a table, button 1 is clicked
and this creates the .bat file and reports the number of records affected by
a MsgBox. I then click button 2 to execute the .bat file and the Command
Prompt window opens and I can watch for success or failure of each command
in the batch file.
If I change the way that I accomplish this task and make it more efficient
by just calling a Function, can I be certain that the file will be created
and closed before the Function to execute the batch file is called?
There is no room for error in this. This entire process is either creating
or deleting Reservations for IP Addresses on 3 DHCP servers located on the
WAN.
Jim
execution of that .bat file.
If I write a procedure that calls procedure 1 (to create the .bat file), can
I be certain that the file will be created and closed before I call
procedure 2 (to execute the .bat file)?
Currently, I use 2 buttons on a form to achieve this. After entering the
data into the form to mark certain records in a table, button 1 is clicked
and this creates the .bat file and reports the number of records affected by
a MsgBox. I then click button 2 to execute the .bat file and the Command
Prompt window opens and I can watch for success or failure of each command
in the batch file.
If I change the way that I accomplish this task and make it more efficient
by just calling a Function, can I be certain that the file will be created
and closed before the Function to execute the batch file is called?
There is no room for error in this. This entire process is either creating
or deleting Reservations for IP Addresses on 3 DHCP servers located on the
WAN.
Jim