To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=77282 Issue #|77282 Summary|RPT: Report fails to run if it exceeeds 176 pages. Component|Database access Version|current Platform|All URL| OS/Version|All Status|NEW Status whiteboard| Keywords| Resolution| Issue type|DEFECT Priority|P3 Subcomponent|none Assigned to|dbaneedsconfirm Reported by|atjensen
------- Additional comments from [EMAIL PROTECTED] Sat May 12 18:33:09 +0000 2007 ------- Test platform: WinXP Home SP2 ( 640 Meg Ram - 32 Video ), JRE 1.6.0._01 Steps to reproduce: Download the first test database from, htp://www.paintedfrogceramics.com/OpenOffice/QA/ReportDesigner/Players2.odb This is a single table flat database with 16,361 records. Runt he report 'First_Fifty_Gone'. This is a simple report against the first 50 records and produces a report of 13 pages. Close the report. Open for edit the query, Query_first_fifty In the SQL view window change the last statement in the query to read: LIMIT 690 Save the query - don't close it - Run the report 'First_Fifty_Gone' again. You should produce a report of 176 pages. A copy of the report produced on my macine is available at: http://www.paintedfrogceramics.com/OpenOffice/QA/ReportDesigner/Players2_690Recs_176Pg.pdf Close the report. Go back to the query and change the number of records to 700, change the last statement to: LIMIT 700 Save the query and close it. Attempt to run the report again. On my machine it fails to run with an error message that the file could not be opened. Now to see if it is the number of pages, or the number of records do the following: Close the current database file. Download the file htp://www.paintedfrogceramics.com/OpenOffice/QA/ReportDesigner/CopyOfPlayers2.odb This file was created by copying Players2.odb, so that we can control just one variable - the report was opened in edit mode and the controls in the detail section where 'tightened' up and the region re-sized to be slightly smaller. With this done, the report can place more records per page. So any changes now should be limited to the report engine, not the database engine. Run the report, 'Fist_Fifty_Gone', there should be no problems. Close the report Open the query 'Query_first_fifty' in edit mode and change the last statement to: LIMIT 700 Save the query Re-run the report, this time it should run to completion as expected, but with a lower number of pages. Now you can use the query to up the record count till it fails again. On my machine the last record count successfull was 760. A copy of the report produced is found at htp://www.paintedfrogceramics.com/OpenOffice/QA/ReportDesigner/Copy_Players2_760Recs_175Pg Change the query to send 770 records and the report fails. To be sure the error was not strictly in ReportDesigner I did the following, but do not have the files available for download. I exported the Master table to a spreadsheet. Then created a new database using the spreadsheet as its data source. Created the same report in this database. Because a spreadsheet sourced Base file does not recognize the LIMIT statement record counts where controlled by deleting or adding rows to the spreadsheet as needed. Bottom line - I was able to produce a report of 176 pages, adding 5 news rows to the spreadsheet caused the same 'can't open file' error when the report was re-run. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
