Disable shift key

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

Guest

I have researched and read every news group message here, but nothing seems
to work. I have an MDB Access 2000 that I am trying to lock down. I have a
security password set for the DB and now I am attempting to prevent bypass
from the shift key. The db has an autoexec macro when opening and the DAO
reference is set.

I have tried all the examples following without any luck.

http://www.mvps.org/access/general/gen0040.htm

I tried Doug Steele's method without luck. I can still get in by holding the
shift key.
ChangePropertyDdl "AllowBypassKey", dbBoolean, False

I tried Joan Wild's method without any luck. DisableShiftKeyBypass() Matter
of fact I keep getting a compile error message, expected:= then the code in
the immediate window disappears when I close it and reopen it.

I looked at Albert Kallal site, but I need something within this DB.

The help menu is rather worthless. Can someone assist me on this, I would
really apprecaiate it? Thanks
 
Hi.
I have a
security password set for the DB and now I am attempting to prevent bypass
from the shift key.
Click to expand...

I hope you are referring to user-level security, not shared-level security,
because the shared-level security (database password) will not prevent
others from bypassing the database application's startup settings by
pressing the <SHIFT> key while opening the database. One must have already
applied user-level security (User ID with user password) in order for the
shift key bypass prevention method to work properly.
I tried Doug Steele's method without luck.
I tried Joan Wild's method without any luck.
Click to expand...

Does "without luck" mean that you are attempting to open the database while
joined to a workgroup other than the workgroup used to secure the database,
and pressing the <SHIFT> key, but you are still able to open the database?
I'll assume so for the rest of this post, but please tell me if I've guessed
incorrectly.

You didn't post links to either of the methods you are referring to, so I'll
assume that these are the methods I've already seen posted. I know that
Joan's and Doug's methods work for properly secured databases and will work
for yours, too, as long as yours is properly secured by applying user-level
security.

If you haven't been attempting to use these methods with shared-level
security applied (which won't work, as I mentioned earlier), and if the
database can be opened without the workgroup file that was used to secure
it, then it isn't secured properly. You've missed a step. Read and study
the Security FAQ to find which step you missed. You can read the Security
FAQ on this Web page:

http://support.microsoft.com/default.aspx?scid=/support/access/content/secfaq.asp

Practice the steps on a copy of your database so that you don't accidently
lock yourself out.

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)
 
Never mind I finally was able to get it work. I don't know what I missed,
but it seems to work now. Thanks for your input.
 
You're welcome.
I don't know what I missed,
but it seems to work now.
Click to expand...

It might be due to being joined to a workgroup other than the correct one
during the tests, but we may never know. Good luck.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)
 
Back
Top