We have an internal application that accesses SQL Server 2000 via ODBC.
The connecton is established with user id and password. We recently
received a business request to allow the software to work with Windows
authentication scheme going forward. This implies that users will no
longer have passwords to login to the database. The Windows PC would
take care of the authentication.
Is there a way (perhaps a connection string) to allow ODBC to connect
to the database in this new environment? I would appreciate any tips
or pointers.<tunity5@.yahoo.com> wrote in message
news:1105712559.798067.299450@.c13g2000cwb.googlegr oups.com...
> Hello,
> We have an internal application that accesses SQL Server 2000 via ODBC.
> The connecton is established with user id and password. We recently
> received a business request to allow the software to work with Windows
> authentication scheme going forward. This implies that users will no
> longer have passwords to login to the database. The Windows PC would
> take care of the authentication.
> Is there a way (perhaps a connection string) to allow ODBC to connect
> to the database in this new environment? I would appreciate any tips
> or pointers.
There are some sample connection strings for trusted connections here:
http://www.able-consulting.com/MDAC...verForSQLServer
Simon|||I think you can call SQLConnect with an empty user name and password
information.
Also, for using SQLDriverConnect, try to add "Trusted_Connection = yes" into
your connect string.
t> The connecton is established with user id and password. We recently
t> received a business request to allow the software to work with
t> Windows authentication scheme going forward. This implies that users
t> will no longer have passwords to login to the database. The Windows
t> PC would take care of the authentication.
Igor Shekalev, http://www.sqledit.com, SQL editor with ODBC support
No comments:
Post a Comment