Grouping on Server / Verify database issue

[PaulNatale]

I am using Crystal Reports 10, and reporting off an Oracle 9 database using the Oracle ODBC driver.

While I am creating the report, it is successfully performing its grouping on the server. Once I close the report and re-open it, it no longer groups on server. If I try to verify the database, I get an error for each table in the report saying that the table no longer exists. Also, whenever I make any change to the report, even something small like changing the font size, the report re-queries data from the database.

When one of my co-workers opens the same report, it behaves just fine. So it seems to be a setting on my computer.

Can anyone point me the right way?

I'm using Crystal 10 with the most recent service pack. My computer is running win 2k.

 

[synapsevampire]

Sounds like someone has the wrong ODBC driver, at any rate, you should be using the Crystal supplied ODBC driver, not Oracles, and better yet, switch to the Crystal supplied native connectivity for Oracle (located under Oracle Server in New connections), it's faster.

-k

 

[PaulNatale]

The native connectivity is definitely faster, and it resolves the Verify Database issue.

However, the report is still not grouping on server for me, and it is still accessing the database when it doesn't need to, like when I change a font size on a column header.

 

[cmmrfrds]

Do you write SQL. If so, then paste the SQL into the Crystal Command and run the SQL from the Command instead of letting Crystal generate the SQL for you. You can save the Commands in the Crystal Repository and resue for other reports. The advantages are; you get the SQL you want, more efficient queries, create reports that would be difficult without preprocessing the data, and take advantage of the powerful Analytical Functions in Oracle.
Using the Command will not prevent Crystal from sending down a query when it is not necessary. I use Oracle OLEDB with the Commands and the queries are sent down to Oracle when it should not be necessary. Crystal Tech Support told me this was by design. To overcome, I put something benign in the where clause so no data is returned when testing the query syntax. For example, where 1 <> 1.
One problem with the Command is that it is not good for syntax checking SQL. I get all my queries working in Toad for Oracle and then paste them into the Command.