|
Crystal Training Faqs/Forums
Top 10 things to know about Report Design
< back
- The Section Format Event handler can be used to change the outcome of a formatted section at runtime. However, code in the Section Format Event handler should not return state for any particular iteration. No matter when or how many times the Format Event handler is called, it should behave the same way. The Format Event handler can be used to calculate values within a ROW and will not provide accurate results if used to accumulate values throughout a record set.
- VB Code cannot be used to create reports on the fly. There is no concept of adding fields to the report at runtime. This means that a Report template must be created at design time in either the RDC (.dsr) or SCR (.rpt) format.
- You may pass a value to a text object at runtime, however, a text object must exist on the report at design time. Passing large amounts of data to a text object may affect the efficiency of your application. Also, since a Text Object is not a Database field, there is NO drill down on this object at runtime.
- When converting multi-table reports from ODBC or Native database connections, you must remove all fields from the report and re-insert them in order to use Active Database connections (using the Active Data Driver P2SMON.DLL).
- Subreports are embedded objects within a report object. Therefore, inserting a subreport from an existing ActiveX Designer file will cause the Format Event code to be lost for the subreport. All subreports should thus be created within a report.
- When saving an ActiveX designer report to Crystal Report (.rpt) format the Section Format Event code will be lost. Reports used in the Crystal Report Designer should be formatted with the SCR formula language.
- The Active Data Driver is designed to work with single result sets. This means that ADO , DAO or RDO should handle all of the linking and SQL manipulation. Although linking multiple result sets within the designer is possible, it will lead to performance losses.
- A set of required Runtime files must be distributed with your application in order to process the reports successfully on a target machine. The list of files may be found in the online help. Also, Visual Basic dependency (.dep) files are included and may be used and modified to meet your needs.
- When employing the Crystal Reports native driver (P2BDAO.DLL) to connect to a secured Access database, you must pass username and password information using the Set Session Info. If the session info is not set with code, the security will be bypassed.
- The RDC Automation Server is not intended to be used for Active Server Page applications. However, the Crystal Reports 6.0 Automation server is. If you are developing an application that needs to be migrated to ASP, we recommend that you use SCR 6.0.
|
|
