SEO

#1 (**permalink**) 02-27-2008, 08:16 PM

We have several machines where multiple people login.
Normally we set the ODBC to 'with NT auth with network
login id'

When we change it from this to 'SQL server auth asking for
login id/pwd' our Visual Basic apps no longer work.

Our VB apps do have a login screen & pwd and that string
is then forwarded to the server, at least we thought it
did.

a copy of our string is as follows:
MudbCn.Open "PROVIDER=MSDASQL;dsn=" & LiveTest & ";uid=" &
gvLogin & ";pwd=" & gvPwd

What do we have to do to properly pass through the ODBC
the loginid and password?

#2 (**permalink**) 02-27-2008, 08:16 PM

I fixed my prb

On PC - Changed ODBC to use SQL & pass loginid & pwd.
On SQL - we have 2 domains - added plain users (not domain
window users) with config for SQL connection (not domain
connection). Then set up security based on that.

>-----Original Message-----
>We have several machines where multiple people login.
>Normally we set the ODBC to 'with NT auth with network
>login id'
>
>When we change it from this to 'SQL server auth asking
for
>login id/pwd' our Visual Basic apps no longer work.
>
>Our VB apps do have a login screen & pwd and that string
>is then forwarded to the server, at least we thought it
>did.
>
>a copy of our string is as follows:
>MudbCn.Open "PROVIDER=MSDASQL;dsn=" & LiveTest & ";uid="
&
>gvLogin & ";pwd=" & gvPwd
>
>What do we have to do to properly pass through the ODBC
>the loginid and password?
>
>.
>

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

ODBC security parameters