If a Report is to list only one source Object Record, then records for any Sub Reports (at the first level) will be defined exclusively by the source SQL Scripts. However, where two or more levels of Sub Reports are used, or where a Report can take multiple Object Records, then each Sub Report selection will span all required records for the entire report scope.
To limit Sub Report records to those relevant to the Parent Object item, a Filter entry must be made in the definition, using the Text property of the Sub Report Control in the Parent Report Object. The syntax of this entry must conform to that used by C1RD, which includes quotes to define a pseudo Where or Filter definition, for example
"TDELOrderLine = " & [PLOLOrderLine]
Here, the Table Field TDELOrderLine is in the child recordset, and these are filtered according to the value PLOLOrderLine which is included in the parent recordset. The syntax conforms to the C1RD scripting tools to create the necessary clause.
Field Formatting
The C1RD includes a range of facilities for aligning and formatting the data values. The one point to note is that all Date and Date / Time data fields should use the following syntax in the Format property of each Control:
dd MMM yyyy HH:mm (or MMMM for full month name)
This syntax is not the default used by C1RD.
The Printed Date control listed in the Footer is a typical example of this requirement.
HighStone Report Registration
Before any Report Design can be used in HighStone as a Report called from the main application panels, the definition must be Registered within the system. Usually HighStone includes a call to this function on the Action Menu where the target report is primarily used - this is shown to Administrator logins only. Use this Action Item to register each report design before use.
It is only necessary to register each report design once, and repeated registrations have no effect. The registration process logs the report definition in the system tables tblMACDocument, and tblMACDocVersion.
Report Registration is not required when Report Formats are integrated in to the system User Reports Library. Note that any Report Format .xml files needed to support User reports must be held in the [Highstone Home]\DocTemplates Folder (and not in the same folder as the .hsr Report Definition).