G
Guest
Setup:
- Windows 2000 Server
- MS SQL2000
I have a VB6 application that modifies a SQL database that, when launched,
prompts the user to enter one of three parameters and press OK:
X (cancels the application)
ALL (modifies all records in the DB that have a null value in a particular
column, changing the null value in that column to a non-null value)
<Registrant ID> (runs the application against the records with the above
parameters, but only for one particular registrant)
The application runs fine when it's launched manually. I specify the ALL
option, click OK and it's done. It also runs fine when a batch file
containing the application name and option (application.exe ALL) is launched
from a command prompt. But when I create a scheduled task calling the batch
file at a particular time, the application fails to run at all.
There is no indication of an error in Scheduled Tasks or Event Viewer, and
the status in Scheduled Tasks shows successful. But the records in the DB
are not modified, and the result window that appears when the application is
finished does not appear.
Any idea why this is happening? I have other batch files that run fine as
scheduled tasks. Is there something about VB applications that prevent them
from running this way?
Thanks!
John Steen
- Windows 2000 Server
- MS SQL2000
I have a VB6 application that modifies a SQL database that, when launched,
prompts the user to enter one of three parameters and press OK:
X (cancels the application)
ALL (modifies all records in the DB that have a null value in a particular
column, changing the null value in that column to a non-null value)
<Registrant ID> (runs the application against the records with the above
parameters, but only for one particular registrant)
The application runs fine when it's launched manually. I specify the ALL
option, click OK and it's done. It also runs fine when a batch file
containing the application name and option (application.exe ALL) is launched
from a command prompt. But when I create a scheduled task calling the batch
file at a particular time, the application fails to run at all.
There is no indication of an error in Scheduled Tasks or Event Viewer, and
the status in Scheduled Tasks shows successful. But the records in the DB
are not modified, and the result window that appears when the application is
finished does not appear.
Any idea why this is happening? I have other batch files that run fine as
scheduled tasks. Is there something about VB applications that prevent them
from running this way?
Thanks!
John Steen