Defaults file settings are used by the runtime engine, Dexterity test mode and Dexterity tools mode.
Each time a Dexterity session is started or your application is launched with the runtime engine, commands, or settings, stored in the defaults file are examined to determine the options that will be used by the developer or by the end-user. This file is created the first time an application dictionary is accessed with the runtime engine or with test mode. If no defaults file exists, it will be created in the Windows directory.
Once you determine custom settings for a defaults file, it can be installed at any workstation using your application. If you don’t install a customized defaults file, a defaults file is created at each computer using your application. The information in the file affects only the computer where the file is located.
The defaults file uses a combination of a setting and a parameter to define defaults file options. The setting is the specific option you want to use, such as the DisplayTableErrors setting and the parameter determines how the setting will be used. In the following illustration, the parameter for the DisplayTableErrors setting is set to TRUE:
In this example, the value TRUE activates the DisplayTableErrors setting, allowing an error ID to be displayed for unknown table errors when they're encountered.
Two kinds of settings can be specified in the defaults file. Both settings can be added to the defaults file using the techniques explained in the Editing the defaults file section of online help.
Additional settings not listed in the Defaults file settings section of online help may appear in your defaults file. For optimal performance, you should not change or remove these settings.
Developer settings function much like system variables except their values are stored indefinitely, until they're changed by the user. Developer defaults settings available for Microsoft Dynamics GP are included in the Microsoft Dynamics GP documentation.