Registry Viewer


The registry viewer enables the user to customize many aspects of the software in order to better serve his or her company.  

Testing Your Registry Entries
The system does not verify the validity of registry entries. Be sure to test your registry entries after completing them to verify that they are functioning correctly.

Setting Values are Uppercase-Lowercase Sensitive:
The Setting Value is case-sensitive: be sure that you enter the value exactly as specified in the documentation. If the documentation specifies a value of true, do NOT enter True or TRUE.

Standard Registry Hierarchy:


When determining which registry entries a specific viewer, report or starter function uses, SAM Pro searches your registry according to a particular 'hierarchy'. This allows entries for specific branches and or users to override main entries. Unless otherwise specified SAM Pro registry entries use the following hierarchy:


sys-viewer-functionid--userid (if Branches are not implemented on your system)

sys-viewer-functionid-branchid (for all users in a Branch, unless overridden by first format)




The first format enables you to specify defaults by branch id and (optionally) user. If this entry is specific to a user, the branch must be specified if a user belongs to a branch.

If branches are not implemented, two dashes (not separated by a space) must precede the user id (as shown in the second option).

The third format enables you to specify defaults by branch id.

The fourth format enables you to specify defaults by security id.

The fifth format pertains to the User Group Id in the User’s parent record (in the upper portion of the User record). You might want to implement this functionality to restrict the access of certain user groups to specific fields in a viewer, or to not display specific viewer tabs.

The last format would apply to all users unless another registry entry was created for their security or branch/user id.

Tip - Reports and Starter Functions: Registry entries for reports replace ‘viewer’ with ‘report’. Registry entries for starter functions replace ‘viewer’ with ‘start.

Export Registry Button
A specific registry entry can be exported by pressing the ’Export Entry’ button on the Registry Viewer. This function would typically be run to provide Data-Basics support with your registry setting for analysis or upgrading purposes.

The system will ask you to select a directory to export the XML file to. Be sure to note the location and filename so that you can easily locate the file. See Start Registry Export and Start Registry Import for information on additional, registry-related functionality.

Important Fields: Lower Pane

The Registry lower pane is sorted alphabetically when it is saved to make it easier look up the settings. They are sorted by the Additional Contents field so that the disabled rows (which begin with an 'x') will be grouped together at or near the bottom of the list.

Setting Key:    Setting Value:

These fields will be set based on the specific registry entry being implemented. Note that the Setting Key is NOT uppercase/lowercase sensitive, but the Setting Value IS case sensitive.

Click here for previous formats.

The field should be checked to disable this registry option.

Case Number: Topic: Default Value:
This internal field is maintained by the system for support purposes.

Topic: Default Value:
These fields display the Help Topic for this registry entry and Default Key Value for this Setting Key. They will be completed for more registry entries in future releases.

Additional Contents:
This field will display the contents of this option as it is actually interpreted by the system.

image\magnifybutton.gif Click the Magnify button to display the detail version of this line. This functionality is useful if you need to enter a long pathname in the Setting Value, for example.

This field may be used to describe this key value. If you included a double exclamation point in


Function Help:
Clicking this button will display the Help Topic for the function this registry entry impacts (if applicable).

Export Entry:
This function creates an XML file that includes the contents of this entry. You would run this function to provide Data-Basics support with your registry setting for analysis or upgrading purposes. The system will ask you to select a directory to export the XML file to. Be sure to note the location and filename so that you can easily locate the file.

Load Settings:
This button should be used with caution. Clicking it will replace the current contents of this registry record with a list of available settings. It is recommended that it only be used when adding new entries, not editing existing ones.

Show Case:
Reserved for Support.

Show Help Topic:
If a Help topic has been created for this registry entry, clicking this button will display it.

Data Conversion Notes:

Converting form 7.1 or below:

Version 7.3 Data Conversion:

Locating Individual Registry Entries

Since registry entries are available for a wide ranges of functions, they cannot all be include in a single help topic. The Help Contents window to the left lists groups the registry entries by subject (e.g., System and Security, Display Options, and so on). Click on a topic (displayed as a purple, closed book) to expand it. In the following illustration, Purchasing has been clicked to display the registry entries pertaining to this subject. Double-click on a topic to display it.


Alternately, if you know the registry id (e.g., sys-newcall) you may use the Index window to look up the topic by entering the Id.

Comparison Against Database

This option (applicable to all registry entries) enables you to prevent copies of your database (which may be running for training or testing purposes) from interfering with "live" operations. Implementing this option in sys-report-serviceinvoice would help avoid inadvertently overwriting your real invoices while running a copy of your data to train new personnel.

You may specify either or both:

Setting Key: eng  Setting Value: enginename

where enginename is replaced by the engine name that your live data runs under.

Setting Key: dbn  Setting Value: databasename

where databasename is replaced by the name of your live database. Do not include the .db extension in the databasename (mydata rather than dbn=mydata.db).