Blocking Access from linking SQL Server tables...

  • Thread starter Thread starter Matthew Wells
  • Start date Start date
M

Matthew Wells

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
(e-mail address removed)
 
If you have given the users permissions, then they have permissions. You
can't deny permissions based on DNS, connection object, etc. Rather than
giving permissions on tables, it may be better for you to create stored
procedures or views, and give them permissions on those instead.

--
Michael Badnarik for President '04
Libertarian...the freedom party
www.lp.org
www.badnarik.org

"If you are in prison and your chances are 50% for execution by electric
chair, 45% for execution by lethal injection, and 5% for escape, are you
just going to vote for the chair because it is the likeliest outcome?" Vote
Libertarian and live to be free.
 
So this guy is endorsing Prison Breaks?

WOW!


Paul said:
If you have given the users permissions, then they have permissions. You
can't deny permissions based on DNS, connection object, etc. Rather than
giving permissions on tables, it may be better for you to create stored
procedures or views, and give them permissions on those instead.

--
Michael Badnarik for President '04
Libertarian...the freedom party
www.lp.org
www.badnarik.org

"If you are in prison and your chances are 50% for execution by electric
chair, 45% for execution by lethal injection, and 5% for escape, are you
just going to vote for the chair because it is the likeliest outcome?" Vote
Libertarian and live to be free.
Click to expand...
 
Back
Top