Apache OpenOffice (AOO) Bugzilla – Issue 77861
RPT: Crash when executing report bound to non-existent table/query, and having groups
Last modified: 2007-09-28 04:07:45 UTC
Open the attached database document. Open report "Join" in edit mode. Goto report property. Make sure that in tab data the type SQL is choosen. It might be changed by document recovery. The SQL is: SELECT * FROM "Landessprache" AS "Landessprache" INNER JOIN "Länder" AS "Länder" ON "Landessprache"."Land" = "Länder"."Code" INNER JOIN "Sprachen" AS "Sprachen" ON "Landessprache"."Sprache"="Sprachen"."Kurz" Run that report. Crash. The same SQL statement works as query. Do not use the query design mode, because it changes INNER JOIN to WHERE.
Created attachment 45446 [details] database with crashing report "Join"
The ID of the error report is rw33pc.
confirm and reassign to the right developer
submitted issue 77892 for the "Content type" being reset to "Table" all the time ...
hmm, cannot reproduce the crash ...
hmm - Marc showed me that he indeed did a modified version of this issue ... If you do *not* change the "Content type" to "SQL command", but execute the report without changing any properties, then it in fact crashes. Regina, can you please confirm that for you, it crashes *after* you changed the "Content type" to "SQL command"? If so, did you save before executing the report?
investigating this further, it seems to boil down to: If the report is bound to a non-existent table or query, or a statement which cannot properly be executed, *and* contains at least one group, then executing it crashes.
grabbing
Created attachment 45486 [details] stripped-down version to reproduce the crash
I checked in a fix for the crash when executing the report *without* changing the "Content type" to "SQL command". Waiting for feedback from regina whether her crash really happened after doing this property change.
The Report Designer iTeam decided that this issue is a show stopper for the release of the report designer. Targeting to 2.3, thus.
I change content type to SQL and insert the SQL-command. If I then execute the report directly, it will not crash. I tested it with execution immediately after inserting the SQL-command and after clicking the save-icon in the designer. But when I close the designer then and execute the report by doublclick or "open", then it crashes.
Addition: I tried it with after saving in the base document window and with before saving in the base document window. Crashes both. When you have entered the SQL-command, make sure that the changes are applied. If your cursor is still in the field it is not applied, but you must click for example the "Allgemein" tab of the property dialog or hit Enter.
okay - this means we talk about the same bug. When you change the properties and execute from within the designer, then the changed properties are applied, which do not crash. When you save and close the report, and execute it by double-clicking, then your changes are *not* applied (this is issue 77892), and thus the report is executed with the old settings - which crash. Changing summary to reflect this, and setting to FIXED. Thanks for the feedback.
fs-> msc: please verify in CWS oj14 build 0.4.0
verified in CWS oj14 version 0.4.0
Tested w/ XP, OOo 2.3 Stable, SRB 1.0.1 Executing now displays error dialog, with correct error statement that table can not be found