Issue 14186 - dBase table very confused which eventually results in OOo crash
Summary: dBase table very confused which eventually results in OOo crash
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 1.1 Beta
Hardware: PC All
: P2 Trivial (vote)
Target Milestone: ---
Assignee: marc.neumann
QA Contact: issues@dba
URL:
Keywords: crash, needmoreinfo, oooqa
Depends on:
Blocks:
 
Reported: 2003-05-06 22:53 UTC by osavill
Modified: 2006-05-31 14:29 UTC (History)
1 user (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 osavill 2003-05-06 22:53:51 UTC
This is going to be very difficult to get accross, but here goes. This happens
on Windows and Linux. It happens in 1.1 beta but NOT in 643C nor 1.0.2.

Use the spead sheet to create a new .dbf file of something like 500 entry rows
with columns of say "Name", "Surname" and "Address". Select the entire table and
drag onto the Bibliography Table tree item to setup a new dBase Biblio data base
table, say "Mailing List".

Unfortunately I cannot attach the real data base since it contains real names
and addresses and the data protection act probably prohibits publication.

Select the Surname column and click the "^A/Z" (Sort A-Z) button. 
Page down a few pages or jump straight to the bottom using the ">|" button. 
Go up a few pages and click in one of the columns.
   The column value changes all by itself !

It appears that rows are missing from the View but no one told the Controller.
Investigation seems to show, for example, the following maybe occuring:
Suppose three entries are in the DB - Smath, Smith, Smyth. What is displayed is:
Smath
Smyth
Clicking in Smyth results in Smith appearing in blue highlight. But I cannot be
really sure. Any how a few clicks like this and the table display starts to get
corrupted, especially if combined with Page Ups and Downs. Then OOo throws and
"Unrecoverable Error"
Comment 1 dankegel 2003-05-11 00:04:15 UTC
corrected version to ooo1.1beta
Comment 2 Frank Schönheit 2003-05-30 11:15:23 UTC
correcting sub component (see
http://www.openoffice.org/issues/describecomponents.cgi?component=database%20access,
please), and resulting default owner
Comment 3 dankegel 2003-06-07 17:14:41 UTC
Correcting platform (since it was reported on both windows and linux)
Comment 4 andreschnabel 2003-07-06 17:06:55 UTC
I cannot confirm this on WinXP / OOo 1.1beta2 (following the
procedure, Owen did suggest).
lowering prio to 3:  product crashes only in very special circumstances
Comment 5 dankegel 2003-07-12 23:10:21 UTC
Can you give us a stack dump of the crash happening in OOo1.1beta2?
See http://kegel.com/openoffice/#dump
(or wait for OOo1.1rc1, which will have a built-in crash logger)
Thanks!
Comment 6 eugenetswong 2003-07-13 21:16:04 UTC
I'm adding the "oooqa" keyword & setting the priority to P1 from P3.
Comment 7 dankegel 2003-09-13 16:12:59 UTC
Hi Owen, can you reproduce this with OpenOffice.org 1.1.0 rc4?

(Changing priority back to 2, since this bug does not
hinder testing in general.  Eugene wasn't following the
guidelines at
http://www.openoffice.org/project/www/issues/bug_status.html#priority )
Comment 8 osavill 2003-09-22 21:46:36 UTC
It will take me a while to reconfirm this issue since it is not my
data base or machine.
Comment 9 prgmgr 2003-10-30 18:31:53 UTC
OOo 1.1.0 has been released now, so please check with this version of OOo.
Comment 10 diane 2003-10-30 19:25:09 UTC
Is this the dBase database included with OOo with the 100MB size
restriction? If so, it possible that these are symptoms of the data
reaching the maximum threshold?
Comment 11 Frank Schönheit 2003-10-31 07:04:42 UTC
there's no size limit for dBase in OOo, sorry. (ehm - not really sorry :).
The limit is in the Adabas D version shipped with *Star*Office, in
OpenOffice.org, there's no limit at all.
Comment 12 diane 2003-11-18 22:20:16 UTC
added needmoreinfo keyword.
Comment 13 marc.neumann 2004-01-05 12:17:37 UTC
Hi,

because no one can reproduce / confirm this I set this issue to invalid. 

Please fell free to reopen this issue if it still occurr. If you reopen this
issue please provide a step-by-step description how I can reproduce this issue.

bye Marc
Comment 14 hans_werner67 2004-02-02 12:16:55 UTC
change subcomponent to 'none'
Comment 15 marc.neumann 2004-04-27 11:03:46 UTC
close