Retrieve ODBC password

[Dedge]

When accessing a linked ODBC data source (ex. SQL Server table), Access
prompts for authentication (ex. id and password) information. Is there a way
to retrieve the user id and password after the ODBC authenitcation process
completes?

TIA

 

[Stefan Hoffmann]

hi,

When accessing a linked ODBC data source (ex. SQL Server table), Access
prompts for authentication (ex. id and password) information. Is there a way
to retrieve the user id and password after the ODBC authenitcation process
completes?

No, not really. What do you like to do with it?

mfG
--> stefan <--

 

[Dedge]

hi,

No, not really. What do you like to do with it?

mfG
--> stefan <--
Hi Stefan:

Thanks for the prompt reply.

I would like to use the User ID and Password to create an ADO connection to
the same data source as the linked table (DB2 in this case), without having
to re-supply authentication info. (This is an MDB).

TIA

 

[Rick Brandt]

Thanks for the prompt reply.

I would like to use the User ID and Password to create an ADO
connection to the same data source as the linked table (DB2 in this
case), without having to re-supply authentication info. (This is an
MDB).

TIA

Passwords would be pretty useless if everyone who knew a little VBA could
steal it (don't you think?).

 

[Dedge]

Passwords would be pretty useless if everyone who knew a little VBA could
steal it (don't you think?).

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com


No Rick, I don't. We are talking about retrieving a password during the execution of an application. The application isn't pulling passwords out of the air - they are being supplied at run-time by authorized users and are only available to the current thread, which assumedly is not doing anything nefarious with passwords.

The only alternative to users' having to enter passwords twice in the
situation I described is for the application to bypass the ODBC login dialog
and supply it's own, which means the password is available to the applicaiton
anyway. This a common and secure practice - I am just looking for a way to
avoid writing another login dialog.

 

[Rick Brandt]

No Rick, I don't. We are talking about retrieving a password during

But they are being supplied to the server with the prompt coming via a
service or API , not to your application nor your code, neither of which has
any business knowing what they are.

 

[Stefan Hoffmann]

hi,

I would like to use the User ID and Password to create an ADO connection to
the same data source as the linked table (DB2 in this case), without having
to re-supply authentication info. (This is an MDB).

Ah, okay. I had this problem once with Oracle. The big problem here,
even if you have the credentials: Using ADO generates a new session, so
any session based DB-logic doesn't work.

Depending on what you like to do: you can use passthrough queries, they
work quite well.


mfG
--> stefan <--