Issue 15083

Summary:	Opening Tables node for Addresses crashes OOo
Product:	Base	Reporter:	Unknown <non-migrated>
Component:	code	Assignee:	marc.neumann
Status:	CLOSED DUPLICATE	QA Contact:	issues@dba <issues>
Severity:	Trivial
Priority:	P3	CC:	issues
Version:	OOo 1.1 Beta2
Target Milestone:	---
Hardware:	PC
OS:	Windows 2000
Issue Type:	DEFECT	Latest Confirmation in:	---
Developer Difficulty:	---

Description Unknown 2003-05-29 22:31:48 UTC

Steps:

1) Set up an Addresses database based on Outlook Contacts. (In my case, I have 
several contacts-type folders, but I don't know whether that's relevant to the 
problem.)
2) View | Data Sources
3) Expand the Addresses data source.
4) Expand the Tables node.

Observed: "An unrecoverable error has occurred."
Expected: No error.

Notes: This worked without problems in 1.1 Beta1.

Comment 1 Frank Schönheit 2003-05-30 08:26:01 UTC

correcting sub component (see
http://www.openoffice.org/issues/describecomponents.cgi?component=database%20access,
please), and changing ownership to QA

Comment 2 Frank Schönheit 2003-05-30 08:27:36 UTC

Hmm. Can't reproduce on my WinXP box.
Tamar, does there appear the crash reporter, which would allow you to
save crash information?

Comment 3 Unknown 2003-05-30 15:29:45 UTC

Yes, I get the message that an error log is being created. Tell me 
where to find the log and I'll attach it.

Comment 4 Frank Schönheit 2003-05-30 16:13:38 UTC

In the crash reporter dialog, there should be a "Save report" button
somewhere. This allows you to save the crash information. If you could
zip it, and attach it here, this may help seeing where it crashed ...

Comment 5 Unknown 2003-06-02 15:33:39 UTC

The dialog I'm seeing doesn't have a Save Report button. It just 
tells me that a report is being created and has a Cancel button.

Comment 6 Frank Schönheit 2003-06-03 08:16:46 UTC

hmmmmm ..... you seem me clueless. Will investigate (which
unfortunately may be after my 3 week vacation, at the earliest).

Comment 7 Frank Schönheit 2003-07-18 10:34:34 UTC

found the other version of this bug ... Tamar, this one here is a
duplicate of 15513, which will be fixed for 1.1.
In case the bug still happens for you with 1.1 (once it's released),
please re-open.

*** This issue has been marked as a duplicate of 15513 ***

Comment 8 Frank Schönheit 2003-07-18 10:34:56 UTC

closing duplicate

Comment 9 hans_werner67 2004-02-02 12:18:53 UTC

change subcomponent to 'none'