Hi,
HELP!!!!!!
I'm using CR4.6 that shipped with Visual Studio 6 (C++). I'm encoutering huge performance problems with CR, because the base query used in the report (like in the Show SQL window in CRW) retrieves a lot of records (10K+). Printing one report takes about 6 minutes. The report is based on 6 joined tables.
I tried to narrow the query (add more conditions in the CRW/Show SQL window), in stead of supplying a selection through SetSelectionFormula(), and the results were terrific (only 3 secs needed to print). But, this "narrowing" should actually be done by the calling program.
So, next thing I tried was to build up the SQL-code from within my VC++ program and using SetSQLQuery() to send the query to the report-class. But this doesn't seem to work. In this case, CR still retrieves 10K records and then tries to create a report based on the complete recordset (about 800 or more pages). That was not what I wanted!
Has anybody had similar experiences? Is there a solution for this problem (other than bying a new CR version...:-( )
BTW: I tried calling GetSQLQuery() after setting the report name, but this results in an empty string. Looks like it's not able to retrieve the SQL from the report.
Any suggestions are welcome!
Martijn
mfigee@jonker-veendam.nl
HELP!!!!!!
I'm using CR4.6 that shipped with Visual Studio 6 (C++). I'm encoutering huge performance problems with CR, because the base query used in the report (like in the Show SQL window in CRW) retrieves a lot of records (10K+). Printing one report takes about 6 minutes. The report is based on 6 joined tables.
I tried to narrow the query (add more conditions in the CRW/Show SQL window), in stead of supplying a selection through SetSelectionFormula(), and the results were terrific (only 3 secs needed to print). But, this "narrowing" should actually be done by the calling program.
So, next thing I tried was to build up the SQL-code from within my VC++ program and using SetSQLQuery() to send the query to the report-class. But this doesn't seem to work. In this case, CR still retrieves 10K records and then tries to create a report based on the complete recordset (about 800 or more pages). That was not what I wanted!
Has anybody had similar experiences? Is there a solution for this problem (other than bying a new CR version...:-( )
BTW: I tried calling GetSQLQuery() after setting the report name, but this results in an empty string. Looks like it's not able to retrieve the SQL from the report.
Any suggestions are welcome!
Martijn
mfigee@jonker-veendam.nl