processing issue.

[Rychertate]

I have an access database that builds a query from linked oracle tables. These tables are very big.
The query in access runs quickly when I launch it.

When I link the access query into my crystal report, I need to sum values of large #s of records. The processing seems to never end.

Is the issue due to linking oracle tables into access rather than importing tables which causes my Crystal Report processing to be slow in summing values from the linked query?

Help.

 

[MJRBIM]

Why not create a stored procedure or view on the Oracle database and write your Crystal Reports directly against it?

 

[Rychertate]

I have Crystal 8.5. Is that Possible?

 

[MJRBIM]

Yes, the query should be created/implemented by your Oracle admin - then you can connect to the view through the Crystal Native Oracle drivers.

 

[synapsevampire]

Define large number of records?

Allowing Oracle to do the processing is optimal, but if the query runs fast in Access, it should be fast from Crystal.

Specifics are required though.

-k

 

[IdoMillet]

The query may seem to be fast simply because Access shows the 1st screen worth of data before the query is done. Try to scroll to the end of the result set and you'll notice it takes time...

If you are not comfortable with Stored Procedures, consider creating another query in access that produces the summarized information. Observe how long it takes and if it's reasonable, use that query as the data source in in Crystal. Access queries show up in Crystal just like any table.

Cheers,
- Ido

CUT, Visual CUT, and DataLink Viewer:
view, e-mail, export, burst, distribute, and schedule Crystal Reports.

http://www.MilletSoftware.com

 

[Smcmanus2001]

I have had this problem with Pervasive, and hopefully this will relate to your probl;em as well. For some reason the Same Query when run directly would be bogg slow in Crystal I created a SQL Query and used the Sql Query Tool in Crystal Reports, and Added the Fields that I needed (the pain in the Butt part of this whole thing). and added the Query to a Fresh Report and trys that, It will run the same speed as the original Query. Remember to add parameters in the Query {?PARAM1}.