To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=106072
                 Issue #|106072
                 Summary|Editing existing chart in report cause crash
               Component|Database access
                 Version|OOO320m2
                Platform|Unknown
                     URL|
              OS/Version|Windows XP
                  Status|NEW
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P3
            Subcomponent|SRB
             Assigned to|dbaneedsconfirm
             Reported by|r4zoli





------- Additional comments from [email protected] Tue Oct 20 07:55:58 
+0000 2009 -------
Open attached odb file.
It created in OOO320m2, copied tables from other file and existing reports,
added to their name "old".
Created some new, in edit mode they showed data, when reports run worked
differently, see attached screenshots in zipped file.
Run reports, some "old reports" worked correctly in m57, not showing chart.
Add new report with table as data source, select szoveg_datum_ertek table.
Add chart into report footer, select chart type, run report, report shows data.
Save report, save file, reopen file, run reports, they not showing chart.
Open report for edit, double click in chart, OS report soffice.bin crash, file
and report edit window remains open, after 30s closed.
Start OOo, file recovery starts and recover file. Close file. Reopen file some
reports showing charts some not. 
It seems to me it is a regression, shows similar symptoms, but not same as it 
was in issue 103588.

---------------------------------------------------------------------
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]

Reply via email to