Entry/Exit Procedures (EEP) are series of commands that can be run within forms, reports, and labels. EEPs provide numerous objectives for versatility in controlling data processing and screen displays.
An EEP can represent a command file that uses the .EEP file extension, or can represent a series of commands embedded with a form, report, or label, which is then referred to as a "Custom EEP". The only difference between an EEP and a Custom EEP is that the Custom EEP is stored in the form, report, or label, whereas a regular EEP must be stored in a command file with the .EEP file extension. An EEP can even be a series of commands that can be executed within a command block of a binary codelocked application file. An EEP can also be a Predefined EEP, which is an EEP option that provides several "predefined" commands when adding buttons to R:BASE Forms.
Custom EEPs were introduced in an effort to decrease the amount of command files stored in a database folder, and to increase portability of a database application. In fact, if you locate all of your EEPs in custom EEPs, you can limit your database folder to just one command file as the startup file. Custom EEPs are now the most common method for storing entry/exit procedures.
EEPs can be executed in the following places:
•Upon entry or exit from a form field
•Upon click, right click, or double click within various form fields
•Upon a key press within some form fields
•Upon the mouse cursor hovering over or leaving a form image
•Upon entry in a row
•Upon exit from a row before updating the row in the database
•Upon exit from a row after updating the row in the database
•Upon changing sections (tables) in the form
•Upon before inserting a row
•Upon after inserting a row
•Before or after a report band
•Before or after a label band
•And more...
EEP Topics:
