ChrisO
06-26-2010, 01:12 AM
G’day all.
From the point of an absolute novice in this area I seek information.
Overall requirement is security when a user tries to log in to an Access 2003 front end which is linked to a SQL Server backend. The SQL server version is unknown but will probably be the second latest, whatever that happens to be.
The ultimate goal is to put the primary responsibility of security on to SQL server to prevent a user from opening any Access front end and reading data. I specifically do not want to store either the user name or their password in the Access front end.
Once SQL server allows entry I will probably write my own internal security for the current Access application, who goes where who sees what…that sort of thing.
I will not be able to test any of this for maybe one or two weeks, we have to setup a hardware/software system.
Security is the name of the game. Suggestions, opinions, links and code are welcome.
Thank you and regards,
Chris.
From the point of an absolute novice in this area I seek information.
Overall requirement is security when a user tries to log in to an Access 2003 front end which is linked to a SQL Server backend. The SQL server version is unknown but will probably be the second latest, whatever that happens to be.
The ultimate goal is to put the primary responsibility of security on to SQL server to prevent a user from opening any Access front end and reading data. I specifically do not want to store either the user name or their password in the Access front end.
Once SQL server allows entry I will probably write my own internal security for the current Access application, who goes where who sees what…that sort of thing.
I will not be able to test any of this for maybe one or two weeks, we have to setup a hardware/software system.
Security is the name of the game. Suggestions, opinions, links and code are welcome.
Thank you and regards,
Chris.