This record enables you place your custom, user-defined and GL reports on Data-Basics report menu. A user-defined function may also be created in order for an SQL script to be run.
Each User Defined function that you create will run one of the following:
A Data-Basics Defined Report
A User Defined Report
A GL Report
Data Import Scripts (available in a future release)
Custom command-line operations
Once you have created a user-defined function, remember to enable it for all User Groups that should have access to it.
Function Id:
A unique Id to identify this function. This field is required. If you are creating this record for a report, we recommend that the Function Id match the Report Id.
Function Name:
This field will default from the Report Name when a Report Id is entered. This field defines how your report or script will appear on Data-Basics Report, Starter or Viewer list. It should clearly define the report or function.
Report Id:
If you are creating a record for a report created for you by Data-Basics, double-click on this field to select from a list of reports. Remember that the report must be imported into your database to appear on the report list.
User Report Id:
If you are creating a record for a report that you created with the User Defined Report function, double-click on this field to select from a list of User Reports.
GL Report Id:
If you are creating a record for a report that you (or a support representative) created with the GL Report function, double-click on this field to select from a list of GL Reports. Remember that if the report was created externally, it must first be imported into your database to appear on this list.
Import Script Id:
This field is reserved for future use.
Application: Application Parameters:
These fields would be completed if you wish to start an application from within Data-Basics software. Typically, this option is used to launch Access with a specific reporting database. The Application field references a registry key of the same name...i.e. "Access" that key would store static path info such as what the *.exe is and what access mdb file to open. The parameter field would hold variable runtime switches to be added to the command line.
Example
Assuming you have a registry entry Access with contents msaccess.exe c:\report.mdb:
Application: Access Parameters = /x myreport
would build a command line...
msaccess.exe c:\report.mdb /x myreport
Menu Category: Report Start Viewer
Select the appropriate menu category under which this item should be listed.