AccessDiscussion of Microsoft Access database design and programming. See also the forums for Access ASP and Access VBA.
Welcome to the p2p.wrox.com Forums.
You are currently viewing the Access section of the Wrox Programmer to Programmer discussions. This is a community of tens of thousands of software programmers and website developers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining today you can post your own programming questions, respond to other developers’ questions, and eliminate the ads that are displayed to guests. Registration is fast, simple and absolutely free .
I have created a user level security database. Everything is working as it should. Here is the problem. I have certain forms that users if they are not cleared for are denied access to and other that if they are cleared for can view. These different forms ultimately are tied to the same table. That is where the problem is. Since the table is used to log info for both viewable and non-viewable forms i have to leave the ability for the underlying table to be read. If i try to prevent the user from read the table then he is denied the use of the forms that he is allowed to view. Therefore i have to leave the table as readable. Therefore i do not where to go. I have to keep the user from viewing a form but yet he could still potentially see the data in the form by simplying opening the underlying table. Any suggestions?
Thanks for the reply, however you can allow edit/additions/deletions without read also activating by default. Then if read if activated by default the use can still see what is in the table? I am stumped.