4D v13.4Undefined |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
4D v13.4
Undefined
Undefined
Undefined returns True if variable has not been defined, and False if variable has been defined. A variable is defined if it has been created via a compilation directive or if a value is assigned to it. It is undefined in all other cases. If the database has been compiled, the Undefined function returns False for all variables. The following code manages the creation of processes when a menu item for a particular module of your application is chosen. If the process already exists, you bring it to the front; if it does not exist, you start it. To do so, for each module of the application, you maintain an interprocess variable ◊PID_... that you initialize in the On Startup database method. When developing the database, you add new modules. Instead modifying the On Startup database method (to add the initialization of the corresponding ◊PID_...) and then reopening the database to reinitialize everything each time you add a module, you use the Undefined command to manage the addition of the new module, on the fly: ` M_ADD_CUSTOMERS global procedure |
PROPERTIES
Product: 4D
INDEX HISTORY
Modified: 4D v11 SQL SEE ALSO |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||