How to restrict users to open a mdb file in design mode?

[bibek24]

Hi,

We have an access application which is accessed through Citrix.
After providing user id and password, if a user clicks 'OK' button of the login screen with holding 'SHIFT' key, the application opens in Design mode which is not secured.

Just wanted to know is there any way to overcome this?
Any properties of the mdb file that we need to enable?
Any code to be written?

Please let me know.

 

[Dennisk]

1) You can hide the database window in the Startup parameters.
2) You can disable the 'special keys'
3) You can convert the front end to an MDE file
4) You can apply Workgroup Security

 

[bibek24]

Hi Dennisk,

I was aware of creating MDE file and also tried for it but it failed to create such,may be due to large size or more no. of components.

Could you please provide me some high level details for the other 3 points you have mentioned?

 

[boblarson]

Perhaps this will help as well:
http://www.mvps.org/access/general/gen0040.htm

 

[pbaldy]

If it failed to create an MDE, the usual suspect is a compile failure. Go into the VBA editor and compile the database. Presuming it errors, fix the error and compile again until it will compile without error.

 

[bibek24]

MDE file is only restricting the forms and reports.But the tables and queries can be still opened in Design mode.

Is there any set up to restrict the tables and queries as well?

 

[MStef]

Hello bibek!
Look at "Demo1A2002.mdb" (attachment, zip).
Try to open it wiht SHIFT button.
It is for users only.

 

[Tanya]

Hi
I found this site which answers your question about disabling "shift" key on startup

http://www.tek-tips.com/faqs.cfm?fid=93

goodluck

 

[pbaldy]

Just so you know, things like the shift key bypass and database window are very easy to get around, and Access security isn't that much tougher to crack. Another idea to consider is either load the runtime version of Access on the Citrix server, or force the users into runtime mode somehow. I've done both. Either should help keep users out of design mode.

 

[Tanya]

Paul
Are you suggesting the Function ap_DisableShift() referred to in the webpage in my previous post is insecure? I am interested for myself because I was intending to use this solution on a database I am working on.
I also lock the properties of my code with a secure password. Is this enough?
Kind regards
Tanya

 

[Mike375]

This topic and variations are frequently posted. Is the fear that someone using the computer will deliberately try and stuff things up or accidentally do something?

I assume the fear is based on a deliberate act because of the posts that talk about "getting around etc."

I am only a small business with a couple of clerical people and telemarketers. The telemarkets will average 6 month so I am getting new people all the time. My own personal experience is that the people are quite frightened that they might stuff something up. In fact what is very common is the new person being showed the program will ask if this is a practice one in case they muck something up.

The only thing I do is have an unbound text box where they enter their driver's licence number and if that is not done then they are blocked from being able to get around the data base. Because only a few key spots are required it only takes me a minute or two to set the version of the DB for their licence number. Perhaps the fact that their password is their driver's licence number makes them feel like the computer system is run by the CIA

I put a shortcut on the task bar to a macro that runs the basic startup in case they accidentally close all of Access or the power drops out etc. Actually, I rarely get accidental closes of Access since I don't use maximised forms and none of the forms have a control box, always a Close at the top centre of the form.

 

[Banana]

MDE file is only restricting the forms and reports.But the tables and queries can be still opened in Design mode.

Is there any set up to restrict the tables and queries as well?

If ULS is correctly implemented, they should have no permissions to create new tables and queries, and for extra measure of security, the data tables should be linked.

You can implement two different workgroup files, one with developer rights and another with just end user's right and distribute only the latter. This is more secure because even if they deciphered the workgroup file, they still only have the permissions and rights of an end user; the developer rights is simply nowhere to be had.

 

[pbaldy]

Paul
Are you suggesting the Function ap_DisableShift() referred to in the webpage in my previous post is insecure? I am interested for myself because I was intending to use this solution on a database I am working on.
I also lock the properties of my code with a secure password. Is this enough?
Kind regards
Tanya

I'm saying that it's sort of like locking your house or car. It will keep the casual user honest. There are all kinds of utilities out there to get around them, and password crackers as well. If someone with a moderate amount of knowledge wants in, those techniques won't even slow them down.

As Mike discussed, if you main intent is to keep people from accidentally messing something up, they should work fine. I just didn't want people to think these were really secure solutions, in case their situation required that.

 

[Tanya]

Paul
I understand now, thank you for your advice.
Regards
Tanya