Shif key bypass

  • Thread starter Thread starter Gerry Goldberg
  • Start date Start date
G

Gerry Goldberg

I would like for only certain users to have the Access startup "Shift key
bypass" available to them. Other (most) users would have this feature
disabled (e.g. no "Shift Key Bypass"). How can I set up my application to
implement this.

Thanks,

Gerry Goldberg
 
Hi Gerry,

The standard security model employed by Microsoft is "security through
obscurity" This means, don't tell the users about the shift key, and
they wont use it.

I know this security model sounds counter-intuitive, but hey, it got
us through last weeks 3 worms ok.

Hahahaha i wanted to carry the gag on for a couple of paragraphs but I
couldnt help it...

Does access even support the concept of users? And I dont mean like
windows 98 either, I mean like actual authenticated, network account
holding users, thats non-breakable by trivial means.
 
Kurt Häusler said:
Hi Gerry,

The standard security model employed by Microsoft is "security through
obscurity" This means, don't tell the users about the shift key, and
they wont use it.

I know this security model sounds counter-intuitive, but hey, it got
us through last weeks 3 worms ok.

Hahahaha i wanted to carry the gag on for a couple of paragraphs but I
couldnt help it...

Does access even support the concept of users? And I dont mean like
windows 98 either, I mean like actual authenticated, network account
holding users, thats non-breakable by trivial means.
Click to expand...

If you use Access User-Level Security then users have to provide a UserName and
Password to use your application. You can then assign different levels of access
based on UserName and/or memberships in various User-Groups that you define. While
not unhackable, (what security model is?), it does require a fairly motivated person
to crack it.
 
This is an all or nothing affair....either the property is on or off. And
it is analyzed BEFORE any code is run. You would only be able to set the
property for the next time your app opens, and if your DB is not split, the
setting will apply to all users. So, it is impossible to do what you want.
 
As mentioned, you can implement security that is generally the best accepted
way to prevent users from using stuff.

In addition, if you are running a multi-user system, then of course you are
giving EACH USER their own front end. So, you could in theory give one
front end to users with the shift key by-pass set.

Further, you probably should be giving each user a mde, and not a mdb. (a
mde is not modifiable by any user).

For info on splitting:

http://www.granite.ab.ca/access/splitapp.htm

http://www.microsoft.com/accessdev/articles/bapp97/chapters/ba15_3.htm

and

http://www.granite.ab.ca/access/autofe.htm
 
Back
Top