>Why you need DSN when you could use SQLSTRINGCONNECT()?
>Just put the whole string in SQLSTRINGCONNECT() and connect to server.

Borislav,

Just to further clarify, the SQL Server connection is to a different application's database, not our own. We've established real-time linking to the other data set to enhance data entry for the user. Subsequently, I don't readily have access to the user's authentication info for the other database.

That brings us to the original question of how I can utilize the info already stored in the ODBC DSN to achieve a smooth transparent logon.

Laterness,
Jon