Issue 56867 - OOo crashes if using wizard for creating form with subforms
Summary: OOo crashes if using wizard for creating form with subforms
Status: CLOSED DUPLICATE of issue 51116
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 2.0
Hardware: PC Windows XP
: P4 Trivial (vote)
Target Milestone: ---
Assignee: christoph.lukasiak
QA Contact: issues@dba
Depends on: 51116
  Show dependency tree
Reported: 2005-10-28 14:08 UTC by cianoz
Modified: 2006-05-31 14:29 UTC (History)
3 users (show)

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


Note You need to log in before you can comment on or make changes to this issue.
Description cianoz 2005-10-28 14:08:58 UTC
I don't have much to say. I simpy verified that if i use the wizard to create a
form with a subform OOo sistematically crashes after confirming the last step of
the wizard. I refer to a MySQL connection (for example the one for which i
uploaded the SQL statement for the issue # 56865)
Comment 1 christoph.lukasiak 2005-11-08 14:38:10 UTC
change owner
Comment 2 christoph.lukasiak 2005-11-08 14:49:19 UTC
clu->cianoz: as i have written in the other issue, we have to check out, what
makes the oo crash, because generally the wizard handles mysql form/subforms
properly (we should have a view on the table structure) - have you the same
problem with smaller (simpler) tables? 

Comment 3 cianoz 2005-11-09 09:49:49 UTC
I made some experiments with new db and forms, much more simple than the one i
experienced problem with, and i had no problem this time.
I think there should be something in more complex databases that causes the
crash using wizard for fhe forms, presumably something related to field used as
relation key.
I shoud make some more test, i hope to find time for it
Thanks for your interesting
Comment 4 christoph.lukasiak 2005-11-30 12:32:07 UTC
lower prio because of the very special case
Comment 5 Mechtilde 2005-12-06 10:30:30 UTC
I want to reopen this Issue.

I had the same problem and  I found one reason for this.

If the database table isn't defined correct OOo crashed without any information.

In my case the mistake was a row defined as "datetime" instead of "date". I
think it's better that nobody can define a row as "datetime"if OO can handle it.

I use MySQl 4.1.11 via ODBc 3.51.09 and OOo many milestones. The last one is
m143. under Debian Sarge
Comment 6 christoph.lukasiak 2006-01-24 12:28:15 UTC
clu->mechtilde: thx for the patience - after a second look, i cannot repro this
issue in an current internal version (2.0.2.), so this issue seems to be fixed -
found out, that this is a duplicate of (i51116) and so a result of the
'datetime' field problem, like you has supposed
Comment 7 christoph.lukasiak 2006-01-24 12:30:26 UTC
Comment 8 christoph.lukasiak 2006-01-24 12:32:02 UTC
duplicate of i54446

*** This issue has been marked as a duplicate of 51116 ***
Comment 9 christoph.lukasiak 2006-01-24 12:33:21 UTC
fixed in 2.0.2.