A: AutoStart : A property setting of a Form that when set to "Yes" will make the application run
    automatically.

B: Bound Control: A control that is dynamically "bound" to a Field in a Table.
    Button: A control on a Form that can have OnClick events associated with it.

<Top>

C: CallForm: A method whereby one Form can call another at run-time.
    CallMacro : A method for calling a Saved Macro.

<Top>

D: Default Form: A SprintDB Pro Form that can be created automatically.

E: Editor: A native SprintDB Pro edit box that allows the user to create Event code or SQL
    statements.
    Event(s): Statements and commands that can be associated with SprintDB Pro Controls. See
    Understanding Macros.

<Top>

F: Form : A container for SprintDB Pro Controls. See also SubForms.
    Functions: See: Database Functions

<Top>

G: Global Variable: SprintDB Pro allows up to 10 Global Variables, 0 - 9. These have the
     pre-defined names: Gvar0 - Gvar9.

L: Lock(Control): A property setting for SprintDB Pro Controls that disables user input.

M: Macro: A collection of Events, Actions and Functions. See Understanding Macros &
    MacroActions.

<Top>

P: Property/Properties : Actions, Events, Functions, etc. associated with SprintDB Pro Controls and Forms. See Setting Properties.

<Top>

Q: Query : An SQL Statement. See Structured Query Language.

R: RecordSource: The name of a SprintDB Pro /Microsoft Pocket Access Table.

S: SubForm: See SubForms Explained, below.
    SQL : See Structured Query Language.

<Top>

T: Tab Control : A control container that allows the user to view an application's controls by tapping
    a "Tab".

<Top>

U: UI = The SprintDB Pro User Interface. See UI Design Guide.

V: Variable: SprintDB Pro allows the use of variables. See Advanced Techniques.

<Top>

SubForms Explained

A SubForm is a form within a form. The primary form is called the Main Form, and the form within the form is called the subform. A Form/SubForm combination is often referred to as a hierarchical form, a master/detail form, or a parent/child form.

Sub forms are especially effective when you want to show data from tables or queries with a one-to-many-relationship. For example, you could create a form with a subform to show data from a Categories table and a Products table. The data in the Categories table is the "one" side of the relationship.

The data in the Products table is the "many" side of the relationship - each category can have more than one product.

The main form and subform in this type of form are linked so that the subform displays only records that are related to the current record in the main form. For example, when the main form displays the Beverages category, the subform displays only the products in the Beverages category.

A main form can have up to 5 subforms. You can also "nest up" subforms. This means you can have a subform within a main form, and you can have another subform within that subform, and so on. For example, you could have a main form that displays customers, a subform that displays orders, and another subform that displays order details. For these types of subforms, you should specify its record source properly to synchronize it with its master form.

For example
The record source of the master form:
"SELECT * FROM Category"
The record source of the subform:
"SELECT * FROM Products WHERE Products.CategoryID=!0!Category.CategoryID"

Please note: !0! refers to MainForm, and !1! refers to SubForm1 and !n! means n-th SubForm.

You can also insert a subform which will not synchronize with any Master form. This type of subform has no parent form. You can specify its RecordSource in event procedures which will be executed at run-time. (e.g: OnOpen event or OnClick event)

<Top>