We have an access project (adp) front-end, and a SQL Server back-end. WE've implemented field-level security module which uses the user's login name when they first login into the system.
The problem we're having is how do we persist security such that the connection to SQL Server does not break every time there is a debug message?
WE don't want to hardcode the username and password in the conection string, since there are different users in the system, whereby the field-level security module is dependent on.
Right now we have a general user name and password entered in the Data Link Properties window, having the Save Password box checked. But that too is the same as hardcoding the username and password in the connection string.
Any ideas?
Thanks in advance.
The problem we're having is how do we persist security such that the connection to SQL Server does not break every time there is a debug message?
WE don't want to hardcode the username and password in the conection string, since there are different users in the system, whereby the field-level security module is dependent on.
Right now we have a general user name and password entered in the Data Link Properties window, having the Save Password box checked. But that too is the same as hardcoding the username and password in the connection string.
Any ideas?
Thanks in advance.
