A key or set of keys on the keyboard that can be used as a “shortcut” to select a menu or menu option rather than using the mouse.
A message that appears when inappropriate, inadequate or unclear data or instructions are issued, when data is not accessible or when a confirmation is required.
A field containing multiple occurrences of the same type of information. The individual pieces of information stored by an array field are called elements. For example, a seven-element array field could be used to store daily sales totals instead of seven individual fields.
The number designating a specific element within an array field. Each component field within an array field has an array index.
A specified portion of the dictionary. For instance, an unused “block” within a dictionary refers to a portion of the dictionary that isn’t being used, or a portion that at one time contained information that has been deleted. You can remove unused blocks by using the compress utility of Dexterity Utilities.
A dictionary that contains portions, or “chunks,” of resources from a source dictionary. Chunk dictionaries allow large dictionaries to be divided into more manageable pieces for delivery to customers. The runtime engine “unchunks,” or merges the chunk dictionaries to re-create the original dictionary. Chunk dictionaries can also be used to deliver updates for an application.
A function of Dexterity Utilities that allows you to transfer “chunks,” or related pieces of information, from a source dictionary to a chunk dictionary. This utility is useful for updating specific portions of a dictionary when the dictionary is very large (such as the Dynamics.dic dictionary). When you’ve modified or added resources in the chunk dictionary, you can merge it back into the source dictionary to implement modifications.
To evaluate the variations between two dictionaries, using Dexterity Utilities.
A string that uniquely identifies the version of your application. You specify the compatibility ID when you add product information to a dictionary. When you launch your application with the runtime engine, the compatibility ID in the application dictionary is compared with the compatibility IDs in the forms and reports dictionaries. If they match, items in the forms and reports dictionaries can be accessed.
The message that is displayed when the compatibility IDs in the forms or reports dictionaries don’t match the compatibility ID in the main dictionary. You specify the compatibility message when you add product information to a dictionary.
To run a script through a compiler. A compiler translates the script instructions into a language that the computer can understand. Once the script has been compiled, the instructions within the script can be executed.
Errors generated when a script is compiled.
The process of removing unneeded information, such as script source, and unused blocks from dictionaries. Dictionaries are typically compressed before being sent to customers.
The control type is the main characteristic of a data type, controlling the type of information that can be stored in fields with the data type, and some aspects of how the information will be displayed. Commonly-used control types are push buttons, integers, check boxes, dates and currencies. See also Data type.
A group of related resources in a Dexterity dictionary that can be referenced by other resources, including forms and reports, throughout the dictionary. Each core module contains one or more specific types of resources such as fields, data types and scripts. See also Dictionary module, Form module and Report module.
Resources such as strings, data types or global fields that are used by several parts of the application. When forms and reports dictionaries are created, the core resources in the application dictionary are copied to them.
If an application uses forms and reports dictionaries, an update should be distributed as a dictionary chunk so the core resources in the forms and reports dictionaries will be updated properly. Otherwise, the application may not work correctly.
Resources that improperly reference other resources. Specifically, scripts referenced by more than one field, table relationships referenced by more than one table, and keys referenced by more than one table are cross-linked resources. The Cross Link Analysis Report checks for these conditions.
A forms or reports dictionary generated by the Modifier and Report Writer.
A Dexterity resource that defines the characteristics for a field, such as its keyable length, control type (push button, check box, string, and so on) and format. A single data type can be applied to several fields, but a field can only have one data type applied to it. See also Control type.
Data types are commonly identified by their control type or storage type; for instance, a radio button data type, or a string data type.
A Dexterity script statement that allows you to create dialog boxes that will appear when an application is run in test mode. For example, the messages appearing in the dialog boxes can be used to indicate which script is being run or the value that should be generated at a given point. If debug statements aren’t compiled, the messages can’t be displayed in test mode. Debug statement messages never appear in applications executed with the runtime engine.
The dictionary to which resources, strings and messages, windows or dictionary modules are transferred, using the Dexterity Utilities.
A group of Dexterity resources that, when interpreted by the runtime engine, present a complete, functioning application.
A group of related core modules. Each core module is placed into one of seven dictionary cores: System, Financial, Sales, Purchasing, Inventory, Payroll and Project. For Microsoft Dynamics GP, dictionary cores typically correspond to Series.
In a launch file, a line that indicates a set of dictionary locations. This set of dictionary locations includes generic pathnames for the locations of the application dictionary, forms dictionary, reports dictionary and any integrating dictionaries. A launch file can contain several sets of dictionary location IDs and dictionary locations.
A group of related resources in a Dexterity dictionary, which can be viewed and transferred using Dexterity Utilities. There are three types of dictionary modules: core, form and report modules. Form and report modules contain resources used only on a specific form or report, such as local fields, scripts and calculated fields, while core modules contain resources that can be used throughout the dictionary. See also Core module, Form module and Report module.
One of the names specified for a table. The display name is used when the name of the table is displayed to the user. See also Technical name.
A dictionary that you can access and work with in a read/write manner.
One of the two procedures that can be associated with a dictionary chunk. When you create a dictionary chunk, you can specify a procedure from the application to be the ending script for the dictionary chunk. The ending script will be run with the other starting and ending scripts after all dictionary chunks have been unchunked. See also Starting script and Installation script.
A function of Dexterity Utilities that copies third-party resources (resources with IDs of 22,000 or greater) you’ve defined in the Dynamics.dic dictionary to a new dictionary.
The dictionary that is created when third-party resources are copied from the Dynamics.dic dictionary to a new dictionary using the Extract utility.
A field contains a single piece of information used by the application dictionary. A field can be displayed in a window or stored in a table. The kind of information the field displays or stores depends upon the data type associated with it. See also Global field and Local field.
See Table.
A collection of windows, menus, scripts and tables that function together for a common purpose.
A user-defined function that’s associated with a specific form.
A group of related resources that compose a specific form.
A procedure that’s associated with a specific form.
Scripts associated with a specific form.
A table that has been attached to a form. Tables must be attached to the form before any window in the form can use the tables.
The extra characters, spacing and attributes that can be applied to a data type when data is entered or displayed.
A data “mask” used for string and composite formats. The format string allows extra characters to appear in a field without affecting the way data in the field is stored.
The dictionary that stores user-modified resources from a main dictionary. This dictionary is created when the Modifier is accessed for the first time. Only copies of the main dictionary’s resources are stored in the forms dictionary. See also Custom dictionaries.
A field created using the Field Definition window. Global fields can be displayed in windows or stored in tables. See also Local field.
A script that isn’t associated with a single window or form but that can be called from other scripts to perform a common function. Renamed “procedure” in Dexterity 3.0.
A procedure in your application that performs actions such as adding items to palettes or setting up default pathnames. Installation scripts are specified as starting or ending scripts for dictionary chunks. When the dictionary chunks are “unchunked,” the installation scripts will run automatically.
A Dexterity application that runs concurrently with another application such as Microsoft Dynamics GP. Integrating applications can use Microsoft Dynamics GP resources.
A field or combination of fields within a record that is used as a basis by which to store, retrieve and sort records.
One field of a group of fields that compose a key.
The number of characters that can be typed in a field.
A file that’s used to start your dictionary with the runtime engine. This file stores the location of your application dictionary, the name and location of any forms or reports dictionaries and the name and location of any integrating dictionaries.
An integer that uniquely identifies the launch file. It appears in the second line of the launch file. This number is also the product ID of the main product. See also Product ID.
A field that’s available only within the form in which it’s created. Local fields are used as window fields. See also Global field.
A message that was entered using the Dexterity Messages window and that can be referenced by its ID in scripts, using the getmsg() function. The message can be displayed using the ask() function or the warning or error statement.
See Dictionary module.
A feature of Dexterity that allows the runtime engine to interpret two or more separate application dictionaries at the same time. This capability allows multiple third-party dictionaries to function with Microsoft Dynamics GP.
Picture objects that are specific, or native, to a particular operating system. Native pictures must be used to create pictures that appear on push buttons and button drop lists.
For tables, the name under which a table is stored by the operating system or database.
For global fields, a shortened version of the field name that is used as the column name when the field is used in a SQL table.
A script that isn't associated with a single window or form but that can be called from other scripts to perform a common function. Referred to as a “global script” prior to Dexterity 3.0.
The ID that’s used to uniquely identify an application dictionary. Product IDs for each product developed with Dexterity must be acquired from Microsoft Business Solutions.
Information added to a dictionary that allows the runtime engine to create a launch file properly.
A complete group of information, such as a customer’s name, address and phone number, made up of one instance of each field in a table. Each record in a table has the same fields.
See Table relationship.
A group of related resources in a Dexterity dictionary that are used to define information that is unique to reports, such as scripts and calculated fields. Resources that aren’t unique to reports, such as fields and tables, are stored in core modules and are referenced within the report definition. See also Core module, Dictionary module and Form module.
The dictionary that stores modified reports from the main dictionary and new reports created with the runtime engine’s Report Writer. The reports dictionary is created when the runtime engine’s Report Writer is accessed for the first time. All reports you modify or create with the runtime engine’s Report Writer are stored in the reports dictionary. See also Custom dictionaries.
An object such as a field, static text, native picture, table, window or script that can be used to create applications in Dexterity.
An internal ID applied to each resource in your application. For each type of resource you create, IDs start at 22,000. For instance, the first data type you create is data type 22,000; the second is data type 22,001, and so on. Resource IDs for Microsoft Dynamics GP start at 1 and never exceed 19,999.
A list of instructions an application uses to perform tasks.
When a dictionary is broken into several chunk dictionaries, the sequence number associated with each dictionary chunk indicates the order in which the dictionary chunks will be “unchunked” and any installation scripts will be run.
A predefined category to which you can assign forms, tables and reports in your application dictionary. Series allow you to more easily organize these resources. If you’re creating an application that links to Microsoft Dynamics GP, assign the appropriate series to your own forms, tables and reports based on the resources they integrate with.
Lists containing the names of forms, reports, tables and table groups in an application dictionary. These lists are used for security, palettes and table maintenance. Dexterity Utilities can be used to manually update these lists.
The dictionary containing the resources to be used in transfers, printing reports, comparing dictionaries or creating chunk dictionaries. A source dictionary has read-only access.
A Dexterity application that operates without integrating with Microsoft Dynamics GP.
One of the two scripts associated with a dictionary chunk. When you create a dictionary chunk, you can specify a procedure from the application to be the starting script for the dictionary chunk. The starting script will be run with the other starting and ending scripts after all dictionary chunks have been “unchunked.” See also Ending script and Installation script.
A picture that’s displayed as part of a data type, such as the picture on a button drop list.
Text that’s displayed as part of a data type, such as the name on a push button or the items in a list box.
One of the standard forms used to store the data in a field. The storage types are: boolean, integer, long, currency, variable currency, string, text, date and time. The control type determines which storage type is used to store the data in the field. See also Control type and Data type.
A sequence of up to 255 ASCII characters. See also String resources.
Sequences of up to 79 characters used throughout an application dictionary for window names, field prompts, static text values and report text.
To specify the native picture on each platform that should be used as the static value for a single data type. When two pictures are synchronized, Dexterity will assign them the same internal ID. Thereafter, when a synchronized picture is displayed by the application as it runs, the native picture that’s appropriate to the current operating system will be displayed.
Synchronize (Dexterity Utilities)
A function that checks all relationships between resources in a dictionary and recalculates all buffer sizes.
A collection of related data formatted in rows. Each row represents a separate record, and each column represents a separate field. Although this term originated with relational databases, Dexterity uses it generically to refer to both relational database tables and ISAM database files.
A group of logically-related tables. For example, a customer master table, a customer address table and a customer history table could all compose a table group. Table groups are used for security and table maintenance.
A link between tables that have fields in common. These relationships allow the Report Writer to select fields from all of the related tables and use them on a single report. Table relationships are set up using the Table Relationship Definition window.
The name used within scripts to refer to a table or window. See also Display name.
To copy specified resources in a source dictionary to a destination dictionary.
The process of dictionary chunks being converted back into a dictionary or being merged with an existing dictionary.
A script in Dexterity that you write and use in the same manner as Dexterity’s built-in functions.
Version numbers (for dictionary chunks)
A dictionary chunk can have a version number associated with it. When the dictionary chunk is “unchunked,” the version numbers are written to the application dictionary. The version numbers can be retrieved from the dictionary and typically are displayed in the application’s About Box.
The work area used to enter and display information in an application.