Issue 61281 - Base crashes when using wizard to create form for mysql database
Summary: Base crashes when using wizard to create form for mysql database
Status: CLOSED DUPLICATE of issue 51116
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 2.0.1
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: dbaneedsconfirm
QA Contact: issues@dba
Depends on:
Reported: 2006-01-29 02:03 UTC by tominbalt
Modified: 2006-05-31 14:29 UTC (History)
1 user (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 tominbalt 2006-01-29 02:03:10 UTC
steps to reproduce:
1. create a new database
2. choose 'connect to existing database' -> JDBC
3. Enter 'jdbc:mysql://localhost:3306/blah' as Datsource URL and
   com.mysql.jdbc.Driver for JDBC Driver (this part all works, I can connect to
4. I choose not to register the database (does not matter) and open for editing
At this point, the mysql tables are visible and the data present and editable
(as a table)
5. Choose 'Forms' -> 'Use Wizard to Create a Form...'
6. Select a table and all fields
7. No subform
8. At this point, if I select the default arrangement 'as a datasheet', all is
fine.  But, if I choose 'Columnar - Labels Left', the form will look wrong
(labels don't line up with entry boxes). Choosing another alignment and going
back to Columnar - Lables Left will fix that and things 'look' fine.
9. Choose the defaults for the next 3 steps (Set data entry, apply styles, set name'
10. Hit finish 3 times (the dialog box doesn't go away).  The first time, the
form looks more 3D, the second, it rearranges itself, the third and OpenOffice

I have repeated this bug with OO2.0 and 2.0.1, mysql JDBC connector 3.1.11 and
3.1.12 and mysql 5.0.18 and 4.1.12.  Mysql database uses innoDB tables and
foreign keys, if that matters.  Database is basically empty and very basic.
Comment 1 marc.neumann 2006-01-30 09:26:02 UTC

Via the search page at
I found that this issue is duplicate to 51116

Bye Marc

*** This issue has been marked as a duplicate of 51116 ***
Comment 2 marc.neumann 2006-01-30 09:26:37 UTC