Apache OpenOffice (AOO) Bugzilla – Issue 6999
calling Bibliography Database crashes OOo
Last modified: 2003-09-08 16:56:16 UTC
I defined a spreadsheet as the Data Source for (Tools - Data Sources - Bibliography - Database type). After this, Tools - Bibliography Database will crash OOo. The spreadsheet was just the standard biblio.dbf transformed to an OOo spreadsheet.
Thanks for posting this issue. Is this a reproducible problem? If so can you list step by step the procedure to consistently reproduce this issue? Please attach any files we need to use to reproduce this issue. Thank you for using and supporting OOo. Unable to duplicate on Win NT 4.0 SP6a, OOo 1.0.1.
I can reproduce it as follows: 1. Open OOo/user/database/biblio/biblio.dbf 2. Save as OOo-spreadsheet, e.g. biblio.sxc 3. In Tools-Data Sources-Bibliography, set the Data source URL to biblio.sxc 4. Open a new text document. 5. Choose Tools-Bibliography Database. This is where my OOo crashes.
Thanks for the additional info. Unable to duplicate on Win NT 4.0 SP6a, OOo 643. Will run test on RH 8.0 later.
I can reproduce this with biblio.dbf (as shiped) in W2K environement. On Linux it works. Build from same source. Error: The instruction at 0x0309cd56 referenced memory at 0x00000007. The memory could not be "read". From debuger, for what if worth: Unhandled exception in soffice.exe (DBTOOLS2.DLL): 0xc0000005: Access Violaiton.
Unable to duplicate RH 8.0, OOo 643. Duplicated on RH 8.0, RH OOo 1.0.1. G. Bürger and Matjaz Godec, if possible test to see if developer build 643 resolves this issue for you.
CP Hennessy <CP.Hennessy@iname.com> send on dev@openoffice.org description with exactly the same symptoms as mine on Thu, 24 Oct 2002 16:33:42 +0100 May be something with w2k environement or compiler. I tried with connectivity/.../drivers/dbase sources from developer release with same result.
I am able to reproduce on RH 7.3. I am using OOo 1.0.1.
Updating contact info.
Do I read this right that the confirmed occurences of this problem all affect OOo 1.0.x, while it cannot be reproduced on OOo643? Can all of you who encountered this please try the latest 643 build and confirm this? I would like to go and mark this issue FIXED then. Thanks!
I cannot reproduce the behavior in 643C (Linux or Windows).
Hi, it does not crash OOo, but nevertheless it still does't work in 643C. Converting biblio.dbf to biblio.sxc does not give a correct bibliography database. None of the column names is correctly assigned. If I try the assignments manually I get a lot of mangling and garbage.
B., * for the "incorrect column names". I assume you mean that after opening the file in Calc, and accessing the .sxc as data source, the column is named e.g. "Identifier,C,50" instead of "Identifier". I don't know if this can be changed (I am cc'ing a senior member of the Calc team to get his opinion), but it would definately be a request for enhancement if you want this to be changed (which sounds reasonable to me, but I am not in the depths of the Calc model). * for the garbage: I do not know what you mean...? I manually adjusted the first row in my .sxc, and everything was fine when viewing it as data soruce table. So when you continue to have a problem with this, please be more precise in your description of what you're doing and what you expect. In any way, I ask you to file new issues when needed. This one here is about the crash. 'Cause you confirmed that this crash does not happen anymore in 643C, I mark this issue as FIXED.
you wrote: * for the garbage: I do not know what you mean...? I manually adjusted the first row in my .sxc, and everything was fine when viewing it as data soruce table. What do you exactly mean by "manually adjusted"? I'd be happy to "adjust" my bibliography file (as .sxc) so that I can use it permanently.
with "manually adjusted" I mean I changed the contents from e.g. "Identifier,C,30" to "Identifier". After this (for every column), everything was fine, so if this doesn't work for you, please submit a new issue where you describe exactly what you're doing and what happens, because this issue here is about the crash (which is not present anymore). Thanks.
closing