Use the Manager to define and set up event handlers using the dialog or tab for the level on which you want to implement the VBA or DLL. Instructions are below.
Access the dialog. It contains a list of all event handlers defined for the context you accessed it for and is empty the first time you access it.
Click to open the dialog. Specify the details of your event handler in the dialog.
Choose the predefined FORMS event for which you want to create an event handler from the box.
Only events from the current context are visible in the box. For example, when you access the dialog from the dialog, the box only contains events that can occur during field processing. When you access it from the dialog, the box contains both events that can occur when forms are processed and events that can occur when fields are processed, since field events are owned by the form definition that contains the fields.
Likewise, when you access the dialog from the menu, you see all events that can occur in FORMS. You can also see events that are related only to the application itself and not to fields, forms, etc. Application-specific events have the prefix "App", for example AppCanClose and AppStart.
Specify any VBA function to be called, the name of a DLL and DLL function, or both.
In the edit box you can specify any data that you want FORMS to make available to the VBA code or DLL. Think of this as parameters to be passed to the event handler, though the semantics differ from the ordinary way of specifying parameters.
When a is specified, click to edit VBA source code in the window.
If you define more than one VBA function for a FORMS event, only the first one on the list is called.
Select as a form definition setting (FORMS Help topic) to bypass Verify and use only external validation and verification. All fields and forms receive Complete status after interpretation, regardless of the result of the interpretation. Then, you can access the data via an event handler or use Transfer to send the output data to another system for verification.
All pre-defined constants used in the VBA editor (for example VB_OK) are color-coded blue. If an undefined constant is used, no compilation error or warning appears. It is defined as 0 and the color changes to black.