AllowByPassKeys

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I know how to set AllowByPassKeys in the current mdb file.
Because of political battles, I am not allowed to use Access Security, so my
question is, is it possible to set this property in another mdb (my back
end), and if so, How?
 
You most certainly can, and should hide all of the ms-access interface. The
options to complete hide and keep people out of the ms-access interface can
easily be done using the tools->start-up options. Using those options allows
you to complete hide the ms-access interface (tool bars, database window
etc). Also, using these options means you
do not have to bother setting up security.

Try downloading and running the 3rd example at my following web site that
shows a hidden ms-access interface, and NO CODE is required to do
this....but just some settings in the start-up.

Check out:

http://www.members.shaw.ca/AlbertKallal/msaccess/DownLoad.htm

After you try the application, you can exit, and then re-load the
application, but hold down the shift key to by-pass the start-up options. If
want, you can even disable the shift key by pass. I have a sample mdb file
that will let you "set" the shift key bypass on any application you want.
You can get this at:

http://www.members.shaw.ca/AlbertKallal/msaccess/msaccess.html

So, to set the shift key in your back end, use the above shift-key
utility.....

I also place a small start form in the back end..and it tells the user they
don't have permissions. when they click ok..the code does a quit...
 
Thanks, Albert. I have all the other parts in place including setting the
AllowBypassKeys in the Front End. Right now, the Back End only has an
AutoExec Macro that Quits the application, so someone with no knowledge can't
get in it. I just want to avoid a somewhat knowledgeable user to be kept out.

If it were not for politicians, we could get some work done. One of the
mangers had a bad experience with a developer who was not skilled with
Security and, you guessed it, she locked it down to where nobody could get
in. So now, "Access Security is Buggy and can't be trusted", but they still
want the data secured.

I need a new job where managers are not ex It people.
 
Change_Err:
If Err = conPropNotFoundError Then ' Property not found.
Set prp = dbs.CreateProperty(strPropName, _ ***** Error 13
varPropType, varPropValue)
dbs.Properties.Append prp
Resume Next

Do I first need to create the property in the target database? The code
would indicate it is trying to create the property, which is what is in the
front end, but not the back end.
 
Do I first need to create the property in the target database? The code
would indicate it is trying to create the property, which is what is in
the
front end, but not the back end.
Click to expand...

Yes....

do note that you have to open the back directly...you can't do this to a
linked back end....

The shift key download does show how to set/un-set the shift key in another
database......
 
Yep, I was just figuring that out. It was interesting in that the code that
failed was trying to create the property.
So, I tried it on one that already has the property appended, and it did work.
Thanks again for the help.
 
Hi,

If I understand you right you want to stop users having access to the
database detail not just hide it.

ie you open database you see and can deal with all.
users only see what you want them to see.

If this is right you can put a front end form on the database with a text
box, and too Buttons Enter and Exit, user enters a password. if pass word
correct it will switch on allow by pass keys, so if you exit and reopen use
shift key you have full access. if the pass word in correct it switches or
keeps allow bypass keys off. the Exit button always switches allow by pass
keys off.

If this is what your after i could send you an example

Dave
 
Back
Top