Hello, I just dealt with a similar problem. Not sure how much of my solution applies to you, but I was using direct connect and pulling data from a query (rather than a table). The problem I found is that in direct connect mode CR filters all of the records itself, which is dreadfully slow!
My...
I finally got CR to do what I wanted, so I thought I would post my results.
The problem was in how I was accessing the DB. Using a direct Access connection is (apparently) really slow because Crystal filters the records itself. Maybe it works better on a table with indexes, but I am using a...
Well, I'm already using an Access query as the data source for the report. CR still filters through all of the returned records instead of just using a WHERE clause.
Should I be using an Access Parameter query instead (and if so, how)? Seems like there were some issues with doing it that way.
Hello,
I'm new to CR, and am having trouble with report performance. Here's what I've got: The report is using Access DB (using direct connect, but I've tried ADO/DAO), I've got a parameter field that I'm using in the record selection formula to limit the data to the records I want.
This all...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.