Monte,

this solution is OK, works very well, but you must be aware of the following risks.

Although none can retrieve the password you saved in the MDB, anyone who runs the MDB will get access to the linked tables, at least in your corporate environment. So, if you hadn't think about (I'm sure you did, but its important to warn less experienced users), you should protect your MDB with password, doing the same with the VBA code.

Either is good to remember that, for the Server, it will be always the same login connecting to , like an "application user".

Unfortunately, i've tried, with no success, to discover how does Ms-Access saves the connection information, once you used one of the linked tables, when you not save the users information with the linked table. I mean, it would be nice to use some login screen with validation by the SQL-Server and then use this information when opening the linked tables on the application.