> You can't really permanently disable it. Nothing in Access is every
> 100 % secure. The only defense you have is ignorance. If a
[quoted text clipped - 13 lines]
>>
>> FA

Signature
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com
Rick,
That would be true through 2003, but would not apply to 2007. The OP did
not state his version. I agree it would be an extra barrier, but, as you
state still hackable.

Signature
Dave Hargis, Microsoft Access MVP
> > You can't really permanently disable it. Nothing in Access is every
> > 100 % secure. The only defense you have is ignorance. If a
[quoted text clipped - 17 lines]
> would be able to re-enable the shift key. ULS is also hackable, but it
> would add an additional barrier layer.
FA - 08 May 2008 16:35 GMT
> Rick,
> That would be true through 2003, but would not apply to 2007. The OP did
[quoted text clipped - 31 lines]
>
> - Show quoted text -
Thanks all for your opinions but i was thinking if we set the file
owner in the code module of disable/enable shift key and if someone
that is not a file owner try to re-enable the shift key then it does
not work unless the file owner tries to do it. The file owner can be
recognized by his/her windows login id. Let me know if this is doable ?
Klatuu - 08 May 2008 16:58 GMT
That wouldn't really help. The AllowBypasskey property can be altered
externally, so the code in the file would not stop that.

Signature
Dave Hargis, Microsoft Access MVP
> > Rick,
> > That would be true through 2003, but would not apply to 2007. The OP did
[quoted text clipped - 37 lines]
> not work unless the file owner tries to do it. The file owner can be
> recognized by his/her windows login id. Let me know if this is doable ?