🚀 go-pugleaf

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

I have been thinking about this one too. When I use any account
except the System the VB app don't even load. So that has noting
to do with ODBC. But, yes, I have set up a source for the user I am
using.

When using the System account the app starts and breaks when trying
to connect with ODBC.  But the big question is: How do i set up an 
ODBC source for the System account? From what I know the System
account is not an ordinary account.

> Also, How are you handling security on the SQL server?
> IS the app hardcoded with password in the connect property?

It is hardcoded into the app. SQL server is set up to handle the
login by it self. I don't use Integrated Security.


I have ordered an upgrade of my VB 3 to VB 4. When I'll get it
I'll try it with a 32-bit VB app.

MICROSOFT DON'T SUPPORT THEIR PRODUCTS!

One thing about Microsoft. I can't get any help from them
because they have a stinking support policy. This is in 
Sweden so I don't know if it's the same elsewhere.
On backoffice products like NT Server there is not a single
day support. I repeat NOT ONE DAY!. On developer products
there is 30 days. But what if I have a problem day 31. The
answer from Microsoft is that I have to buy support by the
hour or to get a separate support agreement.

From my point of view it should be illegal to sell products this way!
Especially when their products don't come free. Microsoft can afford 
it but they seem to invest their money on other things than on 
support. I am normally a  fan of Microsoft but I am a bit scared of 
where Microsoft is going in the future?!

-- orjan

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