Shift Key bypass

  • Thread starter Thread starter Silvester
  • Start date Start date
Can someone tell me how & where to call the shift key bypass code
Function ChangePropertyDdl(stPropName As String, _
PropType As DAO.DataTypeEnum, vPropVal As Variant) _
As Boolean
found at

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

How should I call this function & from where ?
Click to expand...

An even easier solution would be to download an MDB that will set that property
for you. Just go to the following page at Albert Kallal's site:

http://www.attcanada.net/~kallal.msn/msaccess/msaccess.html

Scroll down to the section entitled "By Pass Shift Key Code" and download the
version appropriate to your installation.
 
Thanks. But the code found at that url allows anyone to reset the shift key

Guess what - so does any code that sets the property. Just don't pass that file
around.
 
Not quite Bruce. If you have a secure mdb, and a member of the Admins group
sets the allowbypasskey, only a member of the Admins group (in the mdw that
was used to secure it) can set it back.


In an unsecure mdb, you're quite right. Since the OP is asking this in the
security group, I assume (perhaps wrongly) that the mdb is secure.
 
Not quite Bruce. If you have a secure mdb, and a member of the Admins group
sets the allowbypasskey, only a member of the Admins group (in the mdw that
was used to secure it) can set it back.
Click to expand...

Thanks, Joan. I should have qualified that statement accordingly. I guess I was
having an insecure moment.

:-)
 
You realize that if the DDL parameter of the CreateProperty() call is set to
true, only a member of the Admins group will be able to reset the property?

Cheers,
TC
 
If< the DDL parameter of the CreateProperty() statement is True :-)

I wasn't aware of that particular detail (I have never actually implemented
user-level security *and* setting the AllowBypassKey property together). Thanks,
TC.
 
If< the DDL parameter of the CreateProperty() statement is True :-)
I wasn't aware of that particular detail (I have never actually implemented
user-level security *and* setting the AllowBypassKey property together). Thanks,
TC.
Click to expand...

I guess if I had *looked* at that page at The Access Web, I would have seen that
the article was not addressing the issue of setting the AllowBypassKey property,
but rather about securing the same. Another one landed in that empty space
between my ears!

:-(
 
It raises the question of whether a >non< member of the Admins group can set
that parameter! (thereby creating a property that he can not, thereafter,
alter)

I don't have Access here to try. Anyone like to give it a blast?

Cheers,
TC
 
Back
Top