Registry Report Anywhere File Path (dbreportfiles)

Purpose:

This registry entry identifies the default directory to be used when reports are generated in HTML or PDF for ReportAnywhere. If this directory entry does not exist, reports will default to the directory containing the Data-Basics software executable, v.exe. This registry entry is highly recommended if Report Anywhere is implemented on your system.

Version 9.1 Enhancement

In earlier releases, there was no check to make sure that the path in dbreportfiles directory entry referenced a valid file system directory. In this release:

- If a directory path is found in the Registry, but that path does not exist, an attempt will be made to create that directory.   

- If that directory creation fails (or no Registry entry is found) a default path referencing the 'Reports' sub-directory within the SAMPro directory will be used. That directory will be automatically created if needed.   

- If all else fails, the path to the SAMPro directory itself will be used. This is what previously happened if the Registry entry was absent.

Create PM Billing Spreadsheet

When this function is run, the system will generate a .cvs file listing the results of this function. This report will be loaded into the directory specified by the dbreportfiles registry option.

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.

 

Important Fields:

Id

The Id of the Registry Entry must conform to one of the following formats:

dbreportfiles-branchid-userid

dbreportfiles-securityid

dbreportfiles

The first format enables you to specify the file path 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.

The second format enables you to specify the file path by security id.

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

Description

This field is optional.

Setting Key: directory Setting Value: path

where path is replaced by the full share path to the directory that you want your report files stored in (e.g., C:\databasics\reportanywhere or \\myserver\databasics\reportanywhere).

Important Note on dbreportfiles Directory and Subfolders

The directory specified by this registry entry is expected to contain subfolders xmlToPdf_Sent, xmlToPdf_Failed and xmlToPdf_Retry.  If they don't exist in this directory, they must currently be created manually.

Hint: After saving this entry, remember to exit the software. When you log on again, your file path entry (entries) will be in effect.