◄Summary► ◄Details► ◄Contents► ◄Index► ◄Back► ────────────────────────────────────────────────────────────────────────────── Usage Notes ■ Forms have an associated set of tools - properties, events, and methods - that you can use to define a form's appearance and response to different types of user input. You can uniquely determine the behavior and appearance of each individual form. ■ To create a form module, choose New Form from the File menu. ■ Form modules are private: Event and general procedures contain form modules that cannot be called from external modules or procedures. Form modules do not allow executable code at the module level. ■ Code modules are public: General procedures contain code modules that can be called from other modules or procedures. Executable code is allowed at the module level of code modules. See: ◄Building an Application► ◄Module Definitions► ■ Multiple forms are often used to create an application's user interface. See: ◄Designing Forms► ◄MDI Applications► ■ You can place up to 254 controls on a form. Controls placed on a form are referred to as children, or child controls, of the form. A form cannot get the focus if any of its children are able to receive the focus. See: ◄Parent and Child Relationships► ■ The dimensions of a form correspond to the Height and Width property settings. Settings specified that are less than the minimum value are set to the minimum value. See: ◄Height Property► ◄Width Property► ■ A default-size form with no controls takes approximately 96 bytes of memory. You can use the FRE function to approximate the amount of memory taken up by your own forms. For example: SUB Form_Click () Loaded! = FRE(-1) UNLOAD Form1 Unloaded! = FRE(-1) SHOW PRINT STR$(Unloaded! - Loaded!) END SUB See: ◄FRE Function►