Re: Connecting to linked SQL table in Access
- From: Erland Sommarskog <esquel@xxxxxxxxxxxxx>
- Date: Fri, 14 Mar 2008 15:55:53 -0700
Declan (Declan@xxxxxxxxxxxxxxxxxxxxxxxxx) writes:
ez1 only has read permissions, yet I'm able to update data in the linked
table, and the connect string for the table becomes "ODBC;DRIVER=SQL
Server;SERVER=BackupServer;APP=Microsoft Office
2003;WSID=BACKUPSERVER;DATABASE=bomdSQL;Trusted_Connection=Yes" In
fact, I don't have to even supply a valid logon id and password for me
to be able to link to the table with full permissions. How can I
prevent someone from being able to link to a SQL Server table with full
permissions unless a valid username and passwork is supplied? How can I
make it so the connect string doesn't automatically get set to
"Trust_Connection"?
I have no idea why the connection string changes, but I guess that is a
quirk of Access, and best answered by people who know that product.
However, if users have full access to the table by means of their Windows
login, it's sort of point less if the app restricts the permission.
That can easily be circumvented. So you should make sure that users
do have not any permissions through their Windows login.
--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
.
- References:
- Connecting to linked SQL table in Access
- From: Declan
- Connecting to linked SQL table in Access
- Prev by Date: Re: Trace File with null time SQL2000
- Next by Date: i would like to see who executed a select statement on a specific table
- Previous by thread: Connecting to linked SQL table in Access
- Next by thread: i would like to see who executed a select statement on a specific table
- Index(es):
Relevant Pages
|
