Re: Disable shift key

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: '69 Camaro (ForwardZERO_SPAM.To.69Camaro_at_Spameater.orgZERO_SPAM)
Date: 11/12/04 

Date: Fri, 12 Nov 2004 06:03:31 -0800

You're welcome.

> I don't know what I missed,
> but it seems to work now.

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.)

"Fysh" <Fysh@discussions.microsoft.com> wrote in message
news:F78D1996-AB6E-4E61-895C-13F68D4ECD3B@microsoft.com...
> 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.
>
> "'69 Camaro" wrote:
>
> > Hi.
> >
> > > I have a
> > > security password set for the DB and now I am attempting to prevent
> > bypass
> > > from the shift key.
> >
> > 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.
> >
> > 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.)
> >
> >
> > "Fysh" <Fysh@discussions.microsoft.com> wrote in message
> > news:13DFA8FB-6290-49A7-90E9-BCF33B3C12B5@microsoft.com...
> > > 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
> > >
> > >
> > >
> > >
> >
> >
> >

Relevant Pages

  • Re: Database Ruined
    ... I had no idea setting up security could cause so many ... In a properly secured database, only the owner of that database has ... last time you can view these VERY important settings. ... use the exact same settings when recreating the workgroup. ...
    (microsoft.public.access.security)
  • Re: How to remove password dialog?
    ... I'd like to have no security setting at ... Backup your secure database ... >then open that bak file you renamed. ...
    (microsoft.public.access.security)
  • Re: Access Security not secure
    ... You should secure it manually. ... > In your test with using a new workgroup and running the> wizard it was in access2000 then again in access2002 ... >>> to work well until I try to access the database on the ... >>>>> I created the Administrator and added him to the> admin ...
    (microsoft.public.access.security)
  • Re: Security disapears from menubar when I add a new user
    ... > user logon and created an administrative logon called "sysadmin". ... > database owner is "sysop" and was used for development. ... by creating a new workgroup information file with a unique workgroup ... Security FAQ, ...
    (microsoft.public.access.security)
  • Re: Is someone hacking into our database?
    ... is only about 90-100 mb in size) because the database goes screwy and begins ... but that I know of no way to keep it secure (due to the ... I changed to that workgroup, ... is a member of the Admins Group in system.mdw. ...
    (microsoft.public.access.security)