Saving UID and PWD for ODBC connection

Saving UID and PWD for ODBC connection

Post by Grig » Fri, 14 Jul 2000 04:00:00



I have an Access database with tables linked via ODBC to the corporate SQL
Server database. I use the Access database to perform custom queries and to
extract custom report from SQL Server. I have not any privilege to store
views on the SQL Server.

I set up an ODBC file data source (Control Panel -> ODBC Data Sources) that
connects the SQL database using the SQL Server authenticathion with Login ID
and Password entered by the user (not Win NT authentication). In this way I
can use Access as "custom queries container".

Does anyone know if there is a way to store the Login ID and the Password
without having to type them manually every time? Without saving my
credentials I can't even use the Access queries from third applications
(two-tier architecture in which Access works in the middle as data
pre-aggregator). If I try to connect an Access query via ODBC from a third
application I get  an ODBC error (becuse the queryes are based on linked
tables requiring the Login ID and pwd).

Consider that I'm more an end-user than a programmer. Does anyone can give
me an advice?

Thanks.
Grig

 
 
 

Saving UID and PWD for ODBC connection

Post by John Sui » Fri, 14 Jul 2000 04:00:00


use a connect string to connect to your SQL database which has the username
and password in it, and then save it in a text file or the Access database,
or even have it hard-coded.  Then, when you open the SQL database, use the
connect string and it will connect in the background, without the user
having to enter any information in.

 
 
 

Saving UID and PWD for ODBC connection

Post by gpt » Tue, 18 Jul 2000 04:00:00


You can create a pass through query in Access that connects to the sql
server and thus establishes a connection. Once the connection is
established, Access remembers your credentials and allows you to open up
other tables/ views.

gpt


Quote:> I have an Access database with tables linked via ODBC to the corporate SQL
> Server database. I use the Access database to perform custom queries and
to
> extract custom report from SQL Server. I have not any privilege to store
> views on the SQL Server.

> I set up an ODBC file data source (Control Panel -> ODBC Data Sources)
that
> connects the SQL database using the SQL Server authenticathion with Login
ID
> and Password entered by the user (not Win NT authentication). In this way
I
> can use Access as "custom queries container".

> Does anyone know if there is a way to store the Login ID and the Password
> without having to type them manually every time? Without saving my
> credentials I can't even use the Access queries from third applications
> (two-tier architecture in which Access works in the middle as data
> pre-aggregator). If I try to connect an Access query via ODBC from a third
> application I get  an ODBC error (becuse the queryes are based on linked
> tables requiring the Login ID and pwd).

> Consider that I'm more an end-user than a programmer. Does anyone can give
> me an advice?

> Thanks.
> Grig

 
 
 

1. Saving UID and PWD for ODBC connection

I have an Access database with tables linked via ODBC to the corporate SQL
Server database. I use the Access database to perform custom queries and to
extract custom report from SQL Server. I have not any privilege to store
views on the SQL Server.

I set up an ODBC file data source (Control Panel -> ODBC Data Sources) that
connects the SQL database using the SQL Server authenticathion with Login ID
and Password entered by the user (not Win NT authentication). In this way I
can use Access as "custom queries container".

Does anyone know if there is a way to store the Login ID and the Password
without having to type them manually every time? Without saving my
credentials I can't even use the Access queries from third applications
(two-tier architecture in which Access works in the middle as data
pre-aggregator). If I try to connect an Access query via ODBC from a third
application I get  an ODBC error (becuse the queryes are based on linked
tables requiring the Login ID and pwd).

Consider that I'm more an end-user than a programmer. Does anyone can give
me an advice?

Thanks.
Grig

2. question about dataset and relationship design

3. DAO caches UID and PWD for a given ODBC connection

4. Incrementing field value when record is viewed in web page

5. How to open secured database through ODBC without sending UID and PWD in connection string

6. Security error

7. establishing ODBC connection w/o UID/PWD

8. perl - using mssql without module DBI::ODBC

9. save UID and PWD when creating user DSN

10. Hide UID & PWD in ADP connection

11. System DSN question how to avoid hardcoding a UID and PWD into connection string

12. ODBC login to Sybase without UID, PWD

13. Open database without UID and PWD!!