I do not know what Enterprise is, so I can't help on that one.
I do use SQL to write complex queries, or queries that have heavy date manipulation or data formating (to do it on the oracle server). I also prefer having control of tuning the SQL when going against really large tables (50 to 60 Million records). I have not had any problems with this. I do use CR's selection tools for less complicated reports.
What we are attempting to do is build all of our reports off of a *.qry file. We are using Crystal Enterprise for scheduling reports but it does not seem to work. This may be becuase the reports are based off of the *.qry file. We are now trying to use Seagate Info to schedule the *.qry file to run every morning and then have the reports run off of the updated *.qry file. Does anyone have any other suggestions?
Using a view or a stored procedure is more reliable than using a *.qry file, as well as being faster. Just get your DBA to create a view/stored proc based on the SQL statement you use in your *.qry file. Malcolm Wynden
Authorized Crystal Engineer
I use *.qry file in Enterprise reports and they work fine. Does your report work in regular CR? What version of Crystal Report you have? There are some diff. between 8 and 8.5 and some CR8 reports will not work in Enterprise. My problem is using date parameters with oracle sql. With string I have no problem, I will appreciate your input.
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.