How can I disable Shift key on startup - PERMANENTLY

[DaveG1946]

I have a MS ACCESS 2003 DB which I need to secure against user tampering (both by the curious and the malicious!).

My approach is to:

1. run Access, where the mdb file is on a memory stick;
2. secure the DB with User Level security;
3. split the back end and front end;
4. convert all macros to VBA;
5. disable the shift key through VBA in the back end;
6. convert the back end to MDE (but not name it as ****.mde);
7. hide the back end on the server;
8. re-link the back end;
9. disable the shift key through VBA in the front end;
10. create MDE file for the front end;
11. place the front end mde file on the server in plain sight.

A shortcut to the front end is then placed on the desktop of the client PCs.

All this works well EXCEPT there is a way (Dave Mason et al) in which a user can re-enable the shift pretty simply. This then lets them see what is going on and where the back end is hidden.

I have tried using buttons which only Admins have access to, but the Mason method works anyway

I don't need re-enable the shift key for maintenance. If I need to change the front end I make the change and generate a new mde. If I need to access the back end, I use the mdb on the stick.

Any ideas?

Dave G

[missinglinq]

Putting aside the question of disabling the <Shift> key for the moment, I see two very dangerous things about your approach here.

The Access Gnomes absolutely abhor the use of memory sticks! Being in forced retirement, I've spent an average of 12 hours a day for the past four years on this and half a dozen or so other Access forums, and I've read literally dozens and dozens of sad tales of corrupted databases because of the use of these handy little devices. This MDB file is too critical to risk like this. If you lose it you are truly screwed! Go to the trouble/expense of backing up to a CD.

The second and equally troubling thing concerns having a split multi-user database where the end users are accessing the app by way of a single front end on a shared drive.

Doing this, sooner or later, is going to result in the loss of data thru corruption! The net is also rife with reports of people using this approach for extended periods of time, sometimes for years, without problems, and then suddenly having their apps blow up and start experiencing all sorts of problems, especially those involving timing between two or more users and records becoming inappropriately locked. You simply have to place a copy of the front end on each user's PC.

Linq ;0)>

[DaveG1946]

The stick is only used to transfer the system from my PC to the client's system, so the chances of it being affected by a corruption is small and the effect neglible.

And I forgot to say that the front end MDE is copied from the server to the client PCs.

Sorry for any confusion.

How do I permanently disable the Shift key?

[DaveG1946]

Please ignore my request. After a couple on incidents, I have come to the conclusion that Access security is so full of holes that it isn't the right way to approach the development. Preventing the use of the Shift key is the least of the problems.

[missinglinq]

If security is really an important factor for you, you'd be better off using Access to develop your front end but something elde, such as SQL Server (which does have good security) as the back end.