Apache OpenOffice (AOO) Bugzilla – Issue 11882
Report Wizard Causes OOo644 m1 to crash when importing from dBase database
Last modified: 2006-05-31 14:29:06 UTC
When using the report autopilot in 644m1 to create a report from a dbase data source, the wizard causes OOo to crash with an unrecoverable error during the last step of importing the data into the document. The crash is reproducible. OOo has to be killed off otherwise it just corrupts the screen with a dead window and the error messages. On relaunch, the document can be recovered, but even when you answer yes to all of the questions, the recovered document only contains part of the requested data, the rest of the document is filled with the printers latin that appears in the preview fields during report creation. I tried to import 250 records from my dbase data source.
changing sub component
A question : how is one to know whether its UI or CODE so that I get it right next time ? More info : I just tried repeating the exercise and changing the formatting options to see if that made any difference. Answer : no difference whatsoever, still bombs out. I'm going to try doing it on a query with fewer records to insert and see if that makes a difference.
Tried on a query with 40 records, default formatting. Still bombs out. This looks serious.
> A question : how is one to know whether its UI or CODE so that I get > it right next time ? http://www.openoffice.org/issues/describecomponents.cgi?component=database%20access (just click onto the "Subcomponent" label in this bug form)
Hmm, I've just noticed something strange. The data that's being inserted doesn't always correspond to the field selected. In my previous attempts, I used nearly all of the fields available in my database, with a grouping on one field and a sort on another. Then in my latest tests, I only chose 3 fields, with grouping on one and sorting on another. Each test worked fine, from a not bombing on me point of view, and the document template and corresponding document was created. However, in the example that didn't bomb out, the data corresponding to my COMPANY field was not inserted into the table, and instead the data corresponding to another field was (in this case COADDRESS1) the first line of the address. THis leads to believe that if you select two many fields to be included, OOo perhaps erroneously tries to access and write data from fields that have already been written elsewhere in the table and this is what's throwing the exception. I haven't got time at the moment to try out the maximum number of fields that OOo can deal with without bombing. Maybe there's an error in the basic somewhere ?
msc -> msc: I can reproduce this. Maybe it's the same as the internal bugid 107602. I wait for the bugfix.
fixed
verified in internal build
Hi this issue is fixed in OOo 1.1 Beta2 which is available at http://www.openoffice.org/dev_docs/source/1.1beta2/. I close this bug now. Bye Marc
change subcomponent to 'none'