🚀 go-pugleaf

In article <499u21$svi@stella.tip.net> orjan.esperi@boab.se (Orjan Esperi) writes:
>From: orjan.esperi@boab.se (Orjan Esperi)
>Subject: Scheduling a VB app as a NT AT job?
>Date: Sun, 26 Nov 1995 14:16:29 GMT

Check the ODBC source. The problem maybe your 16bit app attempting to connect 
to a 16bit ODBC sorce not a 32bit ODBC source. You didn't say if the 16bit app 
works WITHOUT sheduler.

>Need some help!

>I've posted this one previously in a few .ms-windows.nt. groups but 
>with no luck yet.

>I am trying to schedule a 16-bit VB/ODBC application to run using the
>AT command. I am using NT Server 3.5.

>At least three question arises.

>QUESTION NO 1:
>Is it possible to connect to an ODBC source 
>using the System account for Schedule? (the ODBC
>source is pointing to a SQL-server database on the same
>machine).

>QUESTION NO 2:
>Is it possible to start a 16 bit VB application using AT/Schedule?

>QUESTION NO 3:
>This is a more general one. What can and can't be done using NT in
>the field of scheduling jobs. What are the limitations? Is there any
>other way to accomplish what I am trying to do?

>Below is a short description of what I tried to do.

>When I start Schedule using the System account with the switch
>"Allow Service to Interact with Desktop" selected the app starts.
>But when the app is doing an automatic  login to an ODBC source
>the login failes with error message:

>"SQLState: '01000', SQL Server Error: 2, [Microsoft][ODBC SQL
>Server Driver][DBNMPNTW]ConnectionOpen (CretateFile()).
>Connection Failed: SQLState: '08001', SQL Server Error: 0
>[Microsoft][ODBC SQL Server Driver]Unable to connect to data source"

>It is my app formatting the message but it's comming from the
>ODBC driver. After this message the default login dialog for the ODBC
>driver displays. When I try to select a database in the combo box the 
>same error occurs again.

>When my first attempt failed I started Schedule using an
>ordinary user account (I created a user with membership in the
>Administrators group). This didn't even start the VB app! The
>only thing showing was an error message: "Unexpected error,
>quitting!".

>Instead of trying to start my app I let AT start Notepad.
>This went fine. A also tried som other 32-bit apps and they seemed
>to work allright. Then I tried several 16-bit applications, none of
>them orked all the way. They either gave me the Unexpected messsage
>or didn't say anything at all or came halfway before quitting. I even
>tried the simplest VB app possible. It too gave me Unexpected....

>I have not tried using 32-bit VB yet.

>Any suggestions and hints are very welcome!

>-- Orjan

>Orjan Esperi
>Business Objects AB
>Zachaus Grans 7
>S-451 30 UDDEVALLA
>SWEDEN