<div>
Hi Lenny, No, but you can define an AutoKeys marco, which will take precedence over anything else. Problem is, not every key combination is allowed, so it may not work for you. As an alternative,you can loop through all the forms in design mode, turn the Key preview on, and then set the properties to the name of a function to call.&nbsp; &nbsp;I have code for this. Jim.
</div>

<div>
Thanks, Jim. I would appreciate that code. The purpose of the sub is to keep the user from accidentally firing a built-in Access reaction to a key (like F1) and to control the forms. So, stopping F4 also stops Ctrl+F4, Alt+F4, Shift+F4, Ctrl+Alt+F4, etc. Once my applications start, I control many aspects. In fact, I will not permit more than one form to be active (or visible) at any time. I even stop the action created by clicking on the "x" in the upper top of a form. All the forms get their own "Exit" button for several control reasons. I was hoping that there was a global-like "event" for the Application object in addition to its methods and properties. I was seeking something like a 'primed' (pipe, shell, socket, etc.) program that "watches" keystrokes while the Access application is running and then intervenes at event. Using a sleep routine consumes too much CPU resources. Thanks, as usual, for your guidance! Lenny 
</div>

<div>
Hello, you can write a public procedure for key handling and use the KeyDown Event to just call this procedure... But Events are connected to objects, so you have to call the procedure from every single form. 
</div>

<div>
Hi Bembi! Thanks for your comment. Your solution is what I am doing currently. I am simply looking for an alternative in the case that I forget to put the key handling code (above) in each of my forms and reports. Also, I would only have one place to change or modify my key handling code. 
</div>

<div>
Yes, using a module keeps the major code on one single place... But triggering the code by events has to be made in every object, where you want to have your key handler.. 
</div>

Developer

Sonny G

<div>
Hi Jim, Thanks for the link! Since that would be a viable solution, I'll mark it as a solution.&nbsp; About 12 years ago, I had to write a class module invoking WithEvents to execute a stored procedure asynchronously. I forgot how to do that since it was a one-off solution to a problem that I had developing the needs of that application. I am going to investigate if I can set a property in that which would be fired with every form's keydown. I'll keep you posted in this thread if I am successful using WithEvents. Lenny 
</div>

<div>
Lenny, &nbsp; That is another solution, but a much more complex one. &nbsp;Far simpler to update each form (programmatically) and set the KeyDown property to a procedure in a general module. &nbsp;Below is an ad-hoc procedure I use for making those kinds of changes. &nbsp; The only issue with this is that you might not want that change for every form. &nbsp; Note that it does both the form and possibly the controls (I comment/un-comment depending on what I need). &nbsp;If you look just before the line #90, there is logic there where I am setting the frm.OnActivateproperty and frm.OnDeactivate to the name of a procedure. &nbsp;The check on the OnClose property is to see if this form is hooked to my framework code or not. &nbsp;If it is, then I wanted to set those other two properties. &nbsp; &nbsp;The property ends up as: &nbsp;=StdFormCT([Form],"OnDeactivateForm","") &nbsp;StdFormCT() is part of my framework code, short for "Standard Form Control". &nbsp; &nbsp;In this way I can easily hook and un-hook things without bothering with classes, and having to hook it all up, along with all the associated overhead that goes with them.&nbsp; &nbsp;If you have any questions on the below, let me know. Jim. <pre><code class="code-10 nolinks" id="code-20-43314682-1">Function DoAllForms_DesignModeChange() As Integer

&nbsp; &nbsp; &nbsp; &nbsp; ' This function loops through all Forms

&nbsp; &nbsp; &nbsp; &nbsp; Dim db As Database
&nbsp; &nbsp; &nbsp; &nbsp; Dim MyDocument As Document
&nbsp; &nbsp; &nbsp; &nbsp; Dim frm As Form
&nbsp; &nbsp; &nbsp; &nbsp; Dim ctrl As Control &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;'Used for controls on form.
&nbsp; &nbsp; &nbsp; &nbsp; Dim lngI As Long
&nbsp; &nbsp; &nbsp; &nbsp; Dim intRet As Integer

10 &nbsp; &nbsp; &nbsp;Set db = DBEngine.Workspaces(0).Databases(0)

20 &nbsp; &nbsp; &nbsp;For lngI = 0 To db.Containers("Forms").Documents.count - 1

30 &nbsp; &nbsp; &nbsp; &nbsp;Set MyDocument = db.Containers("Forms").Documents(lngI)
40 &nbsp; &nbsp; &nbsp; &nbsp;Debug.Print " &gt; Document: "; MyDocument.Name;
50 &nbsp; &nbsp; &nbsp; &nbsp;Debug.Print ""


60 &nbsp; &nbsp; &nbsp; &nbsp;If MyDocument.Name = "frmInvoiceList" Then
70 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;DoCmd.OpenForm (MyDocument.Name), A_DESIGN
80 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Set frm = Forms(MyDocument.Name)

&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 'frm.MaxButton = False
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 'frm.ShortcutMenu = False
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 'frm.NavigationButtons = False
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 'frm.AllowFilters = False

&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 'frm.HelpFile = "HRAPP.HLP"
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 'frm.HelpContextId = 99999

&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 'intRet = glrChangePermission(1, frm.name, "USERS", DB_SEC_FRMRPT_EXECUTE, True)

&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 'If Mid$(NZ(Forms(MyDocument.name).OnClose, ""), 1, 4) = "=Std" Then
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ' &nbsp;frm.OnActivate = "=StdFormCT([Form]," &amp; Chr$(34) &amp; "OnActivateForm" &amp; Chr$(34) &amp; "," &amp; Chr$(34) &amp; Chr$(34) &amp; ")"
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ' &nbsp;frm.OnDeactivate = "=StdFormCT([Form]," &amp; Chr$(34) &amp; "OnDeactivateForm" &amp; Chr$(34) &amp; "," &amp; Chr$(34) &amp; Chr$(34) &amp; ")"
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 'End If

&nbsp; &nbsp; &nbsp; &nbsp;Dim str As String
&nbsp; &nbsp; &nbsp; &nbsp;
90 &nbsp; &nbsp; For Each ctl In frm.Section(1).Controls
&nbsp; &nbsp; &nbsp; &nbsp;
100 &nbsp; &nbsp; &nbsp;str = Replace(ctl.Tag, "EXPAND:", "EXPAND=")
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
110 &nbsp; &nbsp; &nbsp;ctl.Tag = str
&nbsp; &nbsp; &nbsp; &nbsp;
120 &nbsp; &nbsp;Next
&nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 'For Each ctrl In frm.Controls
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ' &nbsp;If ctrl.Section = acDetail Then
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ' &nbsp; &nbsp;With ctrl
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ' &nbsp; &nbsp; &nbsp;' Set afterupdate
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ' &nbsp; &nbsp; &nbsp;Select Case .ControlType
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ' &nbsp; &nbsp; &nbsp; &nbsp;Case acText
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ' &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;strCall = "=StdCtrl(" &amp; Chr$(34) &amp; frm.Name &amp; Chr$(34) &amp; "," &amp; Chr$(34) &amp; ctrl.Name &amp; Chr$(34) &amp; "," &amp; Chr$(34) &amp; "MyAfterUpdate" &amp; Chr$(34) &amp; "," &amp; Chr$(34) &amp; Chr$(34) &amp; ")"
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ' &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;ctrl.AfterUpdate = strCall
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ' &nbsp; &nbsp; &nbsp;End Select
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ' &nbsp; &nbsp;End With
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ' &nbsp;End If
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 'Next ctrl

130 &nbsp; &nbsp; &nbsp; &nbsp; Set ctrl = Nothing

140 &nbsp; &nbsp; &nbsp; &nbsp; DoCmd.Close A_FORM, (frm.Name), acSaveYes

150 &nbsp; &nbsp; &nbsp; &nbsp; Set frm = Nothing
160 &nbsp; &nbsp; &nbsp; End If
170 &nbsp; &nbsp; Next lngI

180 &nbsp; &nbsp; DoAllForms_DesignModeChange = True

End Function
</code></pre>
</div>

<div>
That's a slick piece of code, Jim! Thanks! Lenny 
</div>

<div>
Keep in mind that there is almost nothing you cannot modify via code in Access. Jim.
</div>

<div>
<div class="content wysiwyg-content fr-view">
On each form I have the following sub: Private Sub Form_KeyDown(KeyCode As Integer, Shift As Integer) &nbsp;'*********************** &nbsp;'* Ignore function keys * &nbsp;'*********************** &nbsp; &nbsp; Select Case KeyCode &nbsp; &nbsp; &nbsp; &nbsp; Case vbKeyPageUp &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; KeyCode = 0 &nbsp; &nbsp; &nbsp; &nbsp; Case vbKeyPageDown &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; KeyCode = 0 &nbsp; &nbsp; &nbsp; &nbsp; Case vbKeyPageDown &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; KeyCode = 0 &nbsp; &nbsp; &nbsp; &nbsp; Case vbKeyF1 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; KeyCode = 0 &nbsp; &nbsp; &nbsp; &nbsp; Case vbKeyF2 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; KeyCode = 0 &nbsp; &nbsp; &nbsp; &nbsp; Case vbKeyF3 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; KeyCode = 0 &nbsp; &nbsp; &nbsp; &nbsp; Case vbKeyF4 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; KeyCode = 0 &nbsp; &nbsp; &nbsp; &nbsp; Case vbKeyF5 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; KeyCode = 0 &nbsp; &nbsp; &nbsp; &nbsp; Case vbKeyF6 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; KeyCode = 0 &nbsp; &nbsp; &nbsp; &nbsp; Case vbKeyF7 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; KeyCode = 0 &nbsp; &nbsp; &nbsp; &nbsp; Case vbKeyF8 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; KeyCode = 0 &nbsp; &nbsp; &nbsp; &nbsp; Case vbKeyF9 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; KeyCode = 0 &nbsp; &nbsp; &nbsp; &nbsp; Case vbKeyF10 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; KeyCode = 0 &nbsp; &nbsp; &nbsp; &nbsp; Case vbKeyF11 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; KeyCode = 0 &nbsp; &nbsp; &nbsp; &nbsp; Case vbKeyF12 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; KeyCode = 0 &nbsp; &nbsp; &nbsp; &nbsp; Case vbKeyPageUp &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; KeyCode = 0 &nbsp; &nbsp; &nbsp; &nbsp; Case vbKeyPageDown &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; KeyCode = 0 &nbsp; &nbsp; End Select End Sub Is it possible to place a variation of this code in a global module that would affect all forms throughout the entire application? Thanks, in advance, for your guidance. 
</div>
</div>


On each form I have the following sub:
Private Sub Form_KeyDown(KeyCode As Integer, Shift As Integer)
 '***********************
 '* Ignore function keys *
 '***********************
    Select Case KeyCode
        Case vbKeyPageUp
            KeyCode = 0
        Case vbKeyPageDown
            KeyCode = 0
        Case vbKeyPageDown
            KeyCode = 0
        Case vbKeyF1
            KeyCode = 0
        Case vbKeyF2
            KeyCode = 0
        Case vbKeyF3
            KeyCode = 0
        Case vbKeyF4
            KeyCode = 0
        Case vbKeyF5
            KeyCode = 0
        Case vbKeyF6
            KeyCode = 0
        Case vbKeyF7
            KeyCode = 0
        Case vbKeyF8
            KeyCode = 0
        Case vbKeyF9
            KeyCode = 0
        Case vbKeyF10
            KeyCode = 0
        Case vbKeyF11
            KeyCode = 0
        Case vbKeyF12
            KeyCode = 0
        Case vbKeyPageUp
            KeyCode = 0
        Case vbKeyPageDown
            KeyCode = 0
    End Select
End Sub
Is it possible to place a variation of this code in a global module that would affect all forms throughout the entire application?
Thanks, in advance, for your guidance.

Can KeyDown be coded for Access application-wide or just on each form?

Microsoft Access is a rapid application development (RAD) relational database tool. Access can be used for both desktop and web-based applications, and uses VBA (Visual Basic for Applications) as its coding language.

Microsoft Access

Visual Basic for Applications (VBA) enables building user-defined functions (UDFs), automating processes and accessing Windows API and other low-level functionality through dynamic-link libraries (DLLs). VBA is closely related to Visual Basic and uses the Visual Basic Runtime Library, but it can normally only run code within a host application rather than as a standalone program. It can, however, be used to control one application from another via OLE Automation. VBA is built into most Microsoft Office applications.