Windows is an event driven environment.
Right, there is a huge difference between having events and having to handle them yourself. Regardless of how it's handle, there is an event when you press a key. I'm not trying to stop the event, I'm trying to avoid the user from being able to trigger the event.
I'd be interested in your future post about how you are able to do this.
Private Sub Form_Load()
Me.ShortcutMenu = False
End Sub
Ta da.
If you knew, you wouldn't be saying almost. Almost only counts in horseshoes.
Almost means one thing. I have evidence and experience that leads me to be it's possible but I don't know how. It's why almost everything in science is a theory. It's because they're all almost positive that this is how things work.
You can't capture that in VB6 let alone from VBA. And I really doubt Access casts some magic functionality spell on VBA giving it more power than VB6.
Your replies make it glaringly obvious that you don't have much experience with Access. Do you not see the difference between working in a application and creating a stand-alone application?
Everything in Access, the top menus, the right-click menus, the windows were defined by the code of Access. You can manipulate this as much as the developers of Access want you to manipulate it. ... and believe it or not, Windows allows almost everything to be manipulated.
Please do.
... Oh, and by the way.
Thanks, again, for your help. 
Unsolved 
