[ QUOTE ]
You just posted THE topic that I am curious about myself. My experience has been the same as yours. I created a report (using the OBDC driver - JDE integration which inherits security and columns formatted in JDE format) which joins 4 tables. When I process it using the ODBC driver, the report takes 3+ hours to process. I re-created the same 4 table report using a SQL Server driver, and the report takes 4 seconds to process (no lie!). By using the SQL Server driver, I was forced to re-format all date and amount fields, and I lost the "description" fields.
My question is the same as yours, because if I do not find a way to improve performance, I have to find a way to access the "description" fields.
Calling all Crystal Experts...(report) cleanup on aisle 5!
[/ QUOTE ]
Here is the solution to your problem.
Table Joins
Often, reports need data from several tables. For example, a report displaying an item number from a transaction table may also need to display the item description, which is found in the item master table. This requires a table join.
While it is possible to join tables from within Crystal Reports using table linking, this implementation should be avoided. Reports will experience severe performance degradation if Crystal table linking is used. Crystal will first retrieve records from the master table. Then for each of these records, Crystal will retrieve the record from the joined table.
Recommendation: Table joins should be implemented using (1) business views within enterpriseone or (2) Use a native database view that you can create and then created the it as an EnterpriseOne table, which you can use in Crystal Reports.
Other settings to change on desk tops with crystal that will give you the desired rest are:
(1)XML Fetch Size
The XML Fetch Size setting is located in the registry under HKEY_LOCAL_MACHINE\SOFTWARE\Crystal Decisions\10.0\Crystal Solutions for PeopleSoft EnterpriseOne\QRY.
This determines the maximum number of records that can be retrieved from EnterpriseOne in a single chunk or "page."
The Crystal Reports for PeopleSoft – Integration and Crystal Enterprise for PeopleSoft – Integration installs set the value for the setting to 300. You could set this to 2000
(2) XML Request Timeout
The XML Request Timeout setting is located in the registry under HKEY_LOCAL_MACHINE\SOFTWARE\Crystal Decisions\10.0\Crystal Solutions for PeopleSoft EnterpriseOne\QRY.
The XML Request Timeout setting determines the number of seconds until a single request times out. This setting should be set to a large number to ensure that reports complete.
The Crystal Reports for PeopleSoft – Integration and Crystal Enterprise for PeopleSoft – Integration installs set the value for the setting to 180000. You could set this to 250000
Use the REGEDIT command to do this our you could contact me if you do not know how to do this.