
In Crystal Reports you will need to create a new database connection to the appropriate database, using an OLEDB connection.
If you are using the default Microsoft Access database, it is called "adtempus.mdb" and is found in the "data" subdirectory under the adTempus program directory.
If you are using the MSDE database provided with adTempus, the server is "servername\adtempus", where "servername" is the name of the computer on which the database is installed. The database name is "adtempus"
If you are using using SQL Server, the server is the name of the computer on which the database server is running (generally, the same computer as adTempus is running on). The database name is "adTempus", unless this was changed during installation.
Due to a limitation with the Crystal Reports viewer for .NET, adTempus can only run a report against the same kind of database the report was connected to when it was saved. For example, if you develop your report using a connection to a Microsoft Access database, adTempus can only run that report against a Microsoft Access database. It cannot be run against a SQL Server database.
Similarly, if you are using a SQL Server database, adTempus cannot change between SQL Security and Integrated (Windows) security.
If your reports will only be used with one kind of database (and one authentication model, if you're using SQL Server), this doesn't affect you much. Be sure to specify the report file name in the correct tag when you edit userreports.xml to add your reports to adTempus.
If your reports may be used in different database environments, however, you will need to create a different copy of the report for each environment. adTempus will then select the proper report, based on the database connection being used.
For example, you create your report "myreport.rpt" while connected to the adTempus Microsoft Access database. Once report development is complete, you create a second copy of the report, called, for example, "myreportsql.rpt". In the Crystal Reports Designer, you must change the connection settings for the report to point to a SQL Server database (using SQL Server security) instead of the Access database.
You must then create a third copy of the report, called, for example, "myreportsqlis.rpt". In the Crystal Reports Designer, you must change the connection settings for the report to point to a SQL Server database (using Windows Integrated security) instead of the Access database.
When you edit userreports.xml to include your report in adTempus, you specify all three report files. You also distribute all three report files to the client computers. adTempus will automatically pick the correct version of the report based on the database connection being used.
For an example of this, see "reports.xml", where the Job Accounting Report has both versions listed.
No guide to the adTempus database schema is yet available. Please check the adTempus web site for the latest information on schema availability, or contact us for help figuring out what data you need.
If you plan to include your report in the adTempus Console, adTempus can pass a few parameters to your report. If your report defines these parameters, adTempus will pass a value. Your report only needs to define the parameters that it requires.
|
Name |
Type |
Description |
|
SelectedJobs |
String (allow multiple values) |
A list of the OIDs of the jobs selected by the user in the report's view in the Console. Your report's selection formula should include only those records from the job table where the value of the OID column is in this list. |
|
ServerName |
String |
The name of the computer on which the adTempus service is running (the server from which the data is being taken). |
|
StartDate |
DateTime |
The Start Date selected by the user in the report's view in the Console. |
|
EndDate |
DateTime |
The End Date selected by the user in the report's view in the Console. |
If your report uses additional parameters, Crystal Reports will prompt the user for the values.