Linked tables security

hbrems

has no clue...
Local time
Today, 18:56
Joined
Nov 2, 2006
Messages
181
Dear all,

people can easily bypass the startup 'security' by holding shift. In that way they can see and edit all the tables that are linked to the back-end. Same goes for mde files.

Is there an easy way to prevent users from being able to enter tables. Like a simple password protection without having to set up user accounts and user level security?

Kind regards,
Hans B.
 
If it were easy, everyone would be doing it! Don't like your chances, but I'm no expert in this field
 
Dear all,

people can easily bypass the startup 'security' by holding shift. In that way they can see and edit all the tables that are linked to the back-end. Same goes for mde files.

Is there an easy way to prevent users from being able to enter tables. Like a simple password protection without having to set up user accounts and user level security?

Kind regards,
Hans B.

Hi there.

not quite sure what you are looking for?
why not disable the shift function?

try this link http://www.access-programmers.co.uk/forums/showthread.php?t=36043&highlight=disable+shift+key

regards
rob
 
Did they improve this in the 2007 version by the way?
 
Did they improve this in the 2007 version by the way?

hi hbrems.
i have not used 2007 yet so cant advise on this
2007 looks complicated to me ... i prefer 2000

regards
rob
 
but if you disable shift, can they still get at the system toolbars, or use the window/unhide command to get at the database window.

and even if you prevent them getting at this stuff, you might want to give yourself a back door method of achieving this. Sometimes you have to get directly at your tables and queries for mtce reasons etc
 
but if you disable shift, can they still get at the system toolbars, or use the window/unhide command to get at the database window.

I'm trying to protect my database from the basic users, more then I'm trying to keep the experts out.

I've built custom menu bars, toolbars and shortcut menus (all very minimalistic). I have password protected my code. I'm thinking about providing an mde instead of the default mdb. And now, I have given myself control to allow the shift key or not.

How can they still 'hack' my database? I'm thinking:

- create a new file and import all the current stuff
- ...

Anything else?

I really can't be arsed to use the user level security of Access. It gives me a headache... Certainly in a network environment.
 

Users who are viewing this thread

Back
Top Bottom