vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Good morning... I have an Access front end that uses SQL Server linked tables. SQL Server uses Windows authentication. I have one Windows group that all Access users are a member of. I added that group to SQL Server logins and gave it public, datareader, and datawriter rights to the one database that's used. My front end is locked down, but I want to stop users from creating a new ..mdb and linking SQL Server tables through DSNs or ADO connections or even just importing the links from the actual front end.. I've tried setting the "denydatareader" security policy - that keeps the SQL tables from being seen in the import/link list- but also blocks read rights from the actual front end database. I could set an Access database password on the front end to block importing the links, but that only solves one of the three problems and I want to stay away from Access security altogether. Is there a way to stop users from creating their own DSNs or connection objects or linking tables while still using Windows authentication? Thanks. Matthew Wells MWells@FirstByte.net |