Issue 6999 - calling Bibliography Database crashes OOo
Summary: calling Bibliography Database crashes OOo
Status: CLOSED FIXED
Alias: None
Product: Writer
Classification: Application
Component: ui (show other issues)
Version: OOo 1.0.1
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: Frank Schönheit
QA Contact: issues@dba
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2002-08-15 12:06 UTC by antares
Modified: 2003-09-08 16:56 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description antares 2002-08-15 12:06: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.
Comment 1 prgmgr 2002-09-23 03:17:07 UTC
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.
Comment 2 antares 2002-09-24 13:11:22 UTC
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.
Comment 3 prgmgr 2002-10-23 00:33:30 UTC
Thanks for the additional info.

Unable to duplicate on Win NT 4.0 SP6a, OOo 643.

Will run test on RH 8.0 later.
Comment 4 gody 2002-10-27 00:27:26 UTC
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.
Comment 5 prgmgr 2002-10-27 01:42:44 UTC
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.
Comment 6 gody 2002-10-27 22:21:24 UTC
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.
Comment 7 Unknown 2002-10-29 03:50:04 UTC
I am able to reproduce on RH 7.3.  I am using OOo 1.0.1.
Comment 8 prgmgr 2002-11-11 16:22:32 UTC
Updating contact info.
Comment 9 Frank Schönheit 2002-12-19 14:53:42 UTC
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!
Comment 10 antares 2003-01-14 14:49:20 UTC
I cannot reproduce the behavior in 643C (Linux or Windows).
Comment 11 antares 2003-01-17 12:03:35 UTC
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.

Comment 12 Frank Schönheit 2003-01-17 15:49:08 UTC
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.
Comment 13 antares 2003-01-22 11:38:02 UTC
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.
Comment 14 Frank Schönheit 2003-01-22 12:26:58 UTC
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.
Comment 15 Frank Schönheit 2003-05-20 11:38:13 UTC
closing