S
Sorting in a Graph
How can I restrict some users accessing specific forms/tables? Since 2007
removed user level security; how can 2007 handle this?
removed user level security; how can 2007 handle this?
A
Arvin Meyer [MVP]
It cannot be done for tables. For forms you can roll your own security by
integrating with Windows login username. But since the users can get to the
table that would store this information, it isn't 100% foolproof. The
alternative is to code each form with specific permissions for each user.
To get the Windows login credentials, see:
http://www.mvps.org/access/api/api0008.htm
integrating with Windows login username. But since the users can get to the
table that would store this information, it isn't 100% foolproof. The
alternative is to code each form with specific permissions for each user.
To get the Windows login credentials, see:
http://www.mvps.org/access/api/api0008.htm
C
Citipool
Arvin,
Would you suggest creating a form to act as Login form then use Dev's code
under OnClick property for the Username text box? would that be sufficient
enough? or is there another way to implement it?
Thanks
Would you suggest creating a form to act as Login form then use Dev's code
under OnClick property for the Username text box? would that be sufficient
enough? or is there another way to implement it?
Thanks
A
Arvin Meyer [MVP]
I would use a Login button under the text box. That gives you a bit more
flexibility with the code.
Remember, like a lock, this is security only for honest people who aren't
trying to break it. It provides no more real security than a veil can hide
the face of a beautiful woman.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.accessmvp.com
http://www.mvps.org/access
flexibility with the code.
Remember, like a lock, this is security only for honest people who aren't
trying to break it. It provides no more real security than a veil can hide
the face of a beautiful woman.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.accessmvp.com
http://www.mvps.org/access
A
a a r o n . k e m p f
Access Data Projects can restrict permissions to tables just perfectly
that's why they killed ULS.. because ADP security is sooooo vastly
superior
that's why they killed ULS.. because ADP security is sooooo vastly
superior
C
Citipool
Totally understandable!
Interesting concept!
Interesting concept!
Arvin Meyer said:
A
Arvin Meyer [MVP]
Excuse me, Mr. Kemp, once again you are completely wrong. There is no
different security on an adp than on an mdb. Security has not been "killed"
for MDB's. The no format ACCDB has no equivalent in an ADP because there
haven't been any changes or improvements since Access 2003.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.accessmvp.com
http://www.mvps.org/access
message
Access Data Projects can restrict permissions to tables just perfectly
that's why they killed ULS.. because ADP security is sooooo vastly
superior
different security on an adp than on an mdb. Security has not been "killed"
for MDB's. The no format ACCDB has no equivalent in an ADP because there
haven't been any changes or improvements since Access 2003.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.accessmvp.com
http://www.mvps.org/access
message
Access Data Projects can restrict permissions to tables just perfectly
that's why they killed ULS.. because ADP security is sooooo vastly
superior