Issue 55982 - Base crashes in form wizard
Summary: Base crashes in form wizard
Status: CLOSED DUPLICATE of issue 56203
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOO 2.0 Beta2
Hardware: PC Linux, all
: P2 Trivial with 6 votes (vote)
Target Milestone: ---
Assignee: dbaneedsconfirm
QA Contact: issues@dba
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-14 09:54 UTC by magi
Modified: 2006-05-31 14:29 UTC (History)
1 user (show)

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


Attachments
A simple empty database to produce the problem (3.04 KB, application/vnd.sun.xml.base)
2005-10-14 11:12 UTC, magi
no flags Details
OOo Base odb file (10.93 KB, application/vnd.sun.xml.base)
2005-10-23 07:45 UTC, maxqnz
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description magi 2005-10-14 09:54:04 UTC
This crash occurs always, and corrupts the database, making Base unusable for me.

I created two very simple tables, and then tried to create a form with a subform
with the form wizard. I selected all the fields in the tables to the form, and
linked the tables in the wizard by an id field. Otherwise, I used the defaults.

The tables were empty. The main table (shoppings) contained: id field (integer,
automatic), date/time. The dependant table (items purchased) contained: id field
(integer, automatic), foreign id (for linking to main table), another foreign id
(shop id), floating-point field (price), integer field (quantity).

At the last wizard phase, I clicked Finish. The dialog didn't close, but
something appeared in the form page in the background. I clicked again, again
something happened in the background. Third time, and OOo crashed. Earlier it
has crashed from the first click.

After the database is restored, the second table is usually lost. I think OOo
doesn't save the second table properly to disk after exiting the table design. I
don't know what the problem exactly is, maybe it doesn't save it when exiting
from desing mode, and leaves the Save button disabled in the main view, so it's
not possible to save it manually either.

The crash occurs at least in OOo 2.0 RC2 (and occurred in 1.9.130), Finnish
localized version, from Pavel's builds. Occurs with both jre1.5.0_05 and jre
from j2sdk1.4.2_05. I'm using Red Hat 9, but I've tested the crash also in a
Mandrake computer.

Bug 46116 seemed to have similar problems, though related to Excel sheets.
Comment 1 marc.neumann 2005-10-14 10:46:22 UTC
According to http://www.openoffice.org/scdocs/ddIssues_EnterModify.html#priority
I reduce the prio to P2
Comment 2 magi 2005-10-14 11:12:01 UTC
Created attachment 30425 [details]
A simple empty database to produce the problem
Comment 3 magi 2005-10-14 12:02:50 UTC
The crash does not seem to occur in some situations, but I don't quite know
what. It doesn't seem to matter if the table has some data or is empty, but I'm
not certain.

The crash seems to occur also when I create a simple form, not with a subform,
so using a subform is probably not relevant. Oh, I've set the "in blocks"
control arrangement in the wizard. The crash occurs also when I use English as
GUI language in OOo.

Comment 4 marc.neumann 2005-10-14 12:23:21 UTC
Hi,

I also can reproduce this sometimes. I try to find a way to reproduce this allways.

Bye Marc

Comment 5 maxqnz 2005-10-23 07:45:44 UTC
Created attachment 30732 [details]
OOo Base odb file
Comment 6 maxqnz 2005-10-23 07:49:19 UTC
I have attached a file that replicates this behaviour. In attempting to follow
the excellent beginners' tutorial here, 
http://www.oooforum.org/forum/viewtopic.phtml?t=25060, I found that switching
from "Design Mode On" to "Design Mode Off" invariably caused a silent crash, as
mentioned in the above thread at oooforum.org

Happily, Drew Jensen was able to isolate the problem in the file I attached,
after I noticed that the crash seemed linked to the subform. He discovered, and
I have confirmed, that changing the FormattedField control in the subform to a
Text field stops the crashing. 
Comment 7 broca 2005-10-24 02:07:05 UTC
*** Issue 55982 has been confirmed by votes. ***
Comment 8 broca 2005-10-24 02:12:11 UTC
I have the same problem. OOo Base (2.0 RC02 and the final release, on 
WinXP Home SP2) crashes when I attempt to use the wizard to create a form with a
subform. The program does not crash if I create the same form with subform manually.


Comment 9 Frank Schönheit 2005-10-24 06:55:40 UTC
Note: confirming a crash by votes doesn't make much sense. The goal of the
UNCONFIRMED status is to find a reproducible way to trigger the problem, else,
it cannot be fixed. Votest just say that the problem really happens (nobody
declined this), but doesn't say anything on how to reproduce it.
Comment 10 drewjensen.inbox 2005-10-24 20:26:49 UTC
It seems to be something to do with the use of FormattedFiled controls against
Type Integer columns, when there are no records in the database. It seems to
REQUIRE empty tables. But in the case of at least one of the uploaded database
forms, changing the Integer field control from FormattedField to NuermicField
fixed the problem.

Subsequently I have been able to consistently reproduce both the problem and the
fix. The consistent part is only if this is the very first form created in the
database, after that it seems to go away...

But creating a form with Integers with the wizard and then trying to run it will
always crash, if it is the first form and all tables are empty. Now, edit the
form and change the FormattedField controls to NumericControls, still with empty
table the form will load in active mode no problem.

After this you can create all the forms you like with the wizard, or at least
that seems to be the case with my system.
Comment 11 Frank Schönheit 2005-10-31 15:26:18 UTC
I can reproduce this with the attached employees2.odb
- open the DB doc
- strat the form wizard
- include all fields from "Employees"
- let the wizard generate a sub form, containing all fields from EmployeePhotos
- link EmployeePhotos.EmployeeID to Employees.EmployeeID
- chose "Columnar - Labels left" layout for both the main and the sub form
- finish the wizard
=> crash

I can reproduce this problem in 680m130. I can not reproduce this problem in
680m136 (which will later on be 2.0.1). This issue is most probably a duplicate
of issue 56203, which is a duplicate of issue 55743, which was fixed in 680m134.

*** This issue has been marked as a duplicate of 56203 ***
Comment 12 Frank Schönheit 2005-10-31 15:26:48 UTC
closing duplicate