🚀 go-pugleaf

In article <49emv6$cqr@stella.tip.net> orjan.esperi@boab.se (Orjan Esperi) writes:
>From: orjan.esperi@boab.se (Orjan Esperi)
>Subject: Re: Scheduling a VB app as a NT AT job?
>Date: Tue, 28 Nov 1995 10:06:56 GMT

>Jeffrey, thank you for responding!

>> 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.

>The app works fine when run interactively (without Schedule). It's
>using a 32-bit ODBC source (sql server).

>The app starts when run using Schedule (System account). But it can't
>connect to the ODBC source.

>The app won't even start when using Schedule (User account).

>My problem seem to be rather unique or there is noone out there having
>a solution to it.

>I will post my solution, if I find one...

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

I'm not giving up that easy. Remember ODBC sources are stored under the 
current user. Make sure the scheduler user has the same ODBC source setup. 
Also, How are you handling security on the SQL server? IS the app hardcoded 
with password in the connect property?

Keep in touch with me on this. I want to solve it to.
JK