Preventing end-user seeing tables and relationships

[jworden1]

Hello,

I was wondering if there is any way of stopping people from seeing the tables that I have created and the relationships between said tables?

I want to restrict access so that users can only see the forms and access the reports that I've created but am not sure how to go about stopping people from seeing, never mind altering, the table names and structures. Can anyone help??

 

[KeithG]

Use WorkGroup security

 

[rainman89]

yes. this is how you can do it.
create a switchboard for users to be able to navigate around your system.
then go to tools>startup and uncheck display database window...(to show it you will need to either hold shift on open, or go to Window>unhide)you can also disable the menus and stuff through there.
make sure u set it so that the switchboard opens on startup

If you want it to be even more secure so they cant manipulate the tables... split your db to a frontend and backend. There are tons of threads on that in this forum

 

[KeithG]

If you go this route you also want to disable the shortcut keys. F11 will show the database window.

 

[The_Doc_Man]

The last thing you need to remember is that if you go the route of the switchboard and disable the SHIFT and F11 keys as well, you need to have an "escape route" hidden on the switchboard that is not visible unless the person who logged in is allowed to bypass the switchboard and work directly in the DB window.

In my case, I had a pushbotton that said "Work in Database Window" and it was disabled for most people. But before I got that working correctly, I also had a title that was a Label box. Oddly enough, you can put an OnClick event underneath a label. So I fixed it so that if you clicked on a series of labels in the right order, it would close the switchboard. Of course, there was a trick to it, but then again, I was explicitly being devious at the time.

 

[rainman89]

The last thing you need to remember is that if you go the route of the switchboard and disable the SHIFT and F11 keys as well, you need to have an "escape route" hidden on the switchboard that is not visible unless the person who logged in is allowed to bypass the switchboard and work directly in the DB window.

In my case, I had a pushbotton that said "Work in Database Window" and it was disabled for most people. But before I got that working correctly, I also had a title that was a Label box. Oddly enough, you can put an OnClick event underneath a label. So I fixed it so that if you clicked on a series of labels in the right order, it would close the switchboard. Of course, there was a trick to it, but then again, I was explicitly being devious at the time.

Ah very tricky I like that idea