Issue 66123 - Mailmerge Wizard crash when accessing mysql db via JDBC
Summary: Mailmerge Wizard crash when accessing mysql db via JDBC
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 2.0.3
Hardware: Mac Mac OS X, all
: P2 Trivial (vote)
Target Milestone: ---
Assignee: tino.rachui
QA Contact: issues@dba
URL:
Keywords: crash, oooqa
: 66146 66158 (view as issue list)
Depends on:
Blocks:
 
Reported: 2006-06-05 18:39 UTC by alex.thurgood
Modified: 2008-05-10 21:43 UTC (History)
4 users (show)

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


Attachments
Crash log from crash when using Form letter wizard (28.59 KB, text/plain)
2006-06-15 12:50 UTC, amayze
no flags Details
lsof when mailmerge wizard launched and selecting table in dialog (31.80 KB, text/plain)
2006-08-08 18:21 UTC, alex.thurgood
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description alex.thurgood 2006-06-05 18:39:35 UTC
Accessing a mysql database with MacOSX and the latest mysql jdbc connector, and
2.0.3 RC5 French.

Any attempt to use any of the wizards to access the database that has been
previously set up in an ODB document causes OOo to crash, without any error
message (or perhaps it is hidden, but I don't know where).

I have tried the Letter wizard (withou the ODB document being loaded), the
Report wizard, the Mailmerge wizard, the Database Form wizard.

All of these wizards have a common theme I think : they all use Java

The crash reporter is started next time OOo is started, and tries to recover the
document that was being created, but fails miserably in that all I end up with
is a blank Writer document that has no name (i.e. the default Writer window when
OOo is launched).

Setting crash and oooqa keywords.

Alex
Comment 1 alex.thurgood 2006-06-05 18:43:34 UTC
I might add some more info, because what I gave probably wasn't enough. You can
access the tables and select the fields that you want to appear, but the
application always dies during construction / insertion of the fields and/or data.

This has been tried on single tables, no joins. It is the same database I use on
a day to day basis via MyODBC on Linux. The problem does seem to be Java specific.

Alex
Comment 2 alex.thurgood 2006-06-05 18:45:35 UTC
Forgot to mention that it is the PPC version of 2.0.3rc5
Comment 3 alex.thurgood 2006-06-05 19:44:33 UTC
I would add that I have added the JMF class library and can hear sounds 
correctly from the Gallery so at least some Java components are working 
properly.

Alex
Comment 4 jjmckenzie 2006-06-05 20:11:00 UTC
Adding to issue 65275 (QA tracker.)

James M.
Comment 5 jjmckenzie 2006-06-05 20:11:41 UTC
Make that 65572. 

James M.
Comment 6 jjmckenzie 2006-06-05 20:13:45 UTC
Looks like the wizards are broken again.  Will verify with en-US version.

James M.
Comment 7 jjmckenzie 2006-06-06 02:38:54 UTC
Could not replicate problem with en-US version of 2.0.3rc5.

Not considering this a showstopper for en-US version.

James M.
Comment 8 alex.thurgood 2006-06-06 07:30:22 UTC
Well, further testing has revealed that the Form Wizard and Report Wizard now 
work from within the ODB document. I've got to try the Mailmerge wizard again, 
maybe it was just some form of temporary instability.

Alex
Comment 9 Frank Schönheit 2006-06-06 08:03:36 UTC
people, do you mind considering
http://qa.openoffice.org/issue_handling/basic_rules.html#summary? Thanks :)
Comment 10 alex.thurgood 2006-06-06 09:12:56 UTC
changing summary to reflect more recent information.

Update :

Start OOo. A new untitled Writer document is opened.
Go to Tools > Mailmerge.
Leave the default option "Use active document". Click on "Next"
Leave the default selection of "Letter" in step 2. Click on "Next"
In step 3, click on the button "Select a list of addresses". A window appears
letting you select one of the declared database sources.
Select one and the user name and password dialog appears.
Then a table selection dialog appears. Select a desired table. Click on "OK"

Bang. OOo dies, all windows disappear. No error message. Nada.

Reproducible 100%. I've now done this 10 times.

@James : could you try and confirm this for me please ?

Alex

Comment 11 alex.thurgood 2006-06-06 09:26:26 UTC
@fs : sorry Frank, that was my fault :-(, it has always annoyed me that you 
can't set the keywords when you enter the bug the first time around, and in my 
haste, I took the title for the keyword field. Corrected now.

Alex
Comment 12 christoph.lukasiak 2006-06-07 11:38:11 UTC
(generally it works fine in a 680m171 => seems to be a mac only bug)

clu->jogi: like we have spoken, please check if you can, and/or send further to
corresponding person from mac project

thx
Comment 13 amayze 2006-06-14 17:09:50 UTC
I can confirm that this bug is present in 2.0.2 en-GB.
It happens when the database being used is a OOo spreadsheet, and when using
either the Mail Merge Wizard or the option to print a form letter when printing
a document with database fields in it.

I can submit crash logs if it would help.

Andy
Comment 14 alex.thurgood 2006-06-14 20:41:45 UTC
@amayze : yes, please do enclose the crash reports as attached files to the 
issue. You don't say which platform you are using - Mac(PPC), Intel(Win,Mac,
Linux, etc), or other ?

Alex
Comment 15 amayze 2006-06-15 12:48:12 UTC
Sorry, forgot the extra info:
I'm running MacOS X 10.4.6 on an Intel iMac
Will attach crash report now too.

Andy
Comment 16 amayze 2006-06-15 12:50:22 UTC
Created attachment 37174 [details]
Crash log from crash when using Form letter wizard
Comment 17 amayze 2006-06-16 11:35:29 UTC
I've now tried this on a PPC Mac with 10.3.9 using OOo 2.0.1, 2.0.2 and 2.0.3rc5
en-GB.
I've also now installed J2SE 5.0 Release 4 and OOo 2.0.3rc5 en-GB on the Intel
iMac and it also now works.

Andy
Comment 18 alex.thurgood 2006-06-27 08:56:20 UTC
Hi all

Just tested in rc6. The crash still occurs :-((  This means that I can't migrate
out 2 Mac machines to 2.0.3 at work

Alex
Comment 19 jjmckenzie 2006-06-27 15:18:14 UTC
Just adding my comments here:

1. RC7 is on its way.
2. This appears to affect both PPC and Intel versions.
3. Thank you for the summary update.
4. It appears that Java 5.0 fixes this problem, but is broken with Java 1.4 as 
supplied by Apple.
5. This issue does not affect FreeBSD/OpenBSD? (This is a question that needs 
to be answered and I do not have one of these systems to test with.)

James M.
QA Lead PPC
Comment 20 alex.thurgood 2006-06-27 23:10:31 UTC
Jim,

Aha, well I do have a FreeBSD 6 (PC-BSD 1.0) with OOo 2.0.2 installed and self
compiled JDK 1.4 and 1.5. I have longstanding issues with Java functionality
stability and OOo, but it appears that it is par for the course because it is
such a b*gg*r to build. My OOo is binary package install, no room to compile it
on my disk. I couldn't get the 2.0.3 binary to install, kept giving me an error.

Also have the same issues with playing multimedia files from within OOo, even
with the JMF installed.

Alex 
Comment 21 Joost Andrae 2006-08-01 14:52:23 UTC
please don't file P2 issues as P1
Comment 22 alex.thurgood 2006-08-01 15:48:10 UTC
@ja : are you implying then that being able to connect to a database and having 
it systematically and reproducably bring down the app is not a P1 ? I'm sorry, 
but I beg to differ, from the reading I have of the help associated with 
prioritizing.

Let me add some more info. If you switch the default Address database provided 
to a mysql database, then you can not even press F4 and have the tree view show 
up without OOo crashing in MacPPCrc7. How close does that get to making the 
application as a whole unusable ?

I am assuming from your comment that core functionality doesn't include being 
able to access your database without bringing down the app as a whole.
Comment 23 jjmckenzie 2006-08-02 04:12:50 UTC
@wurzel

What version of MySQL are you using?  Can you provide a data extract and .odt to
run the merge against?  This is for verification testing purposes only.

James M.
Comment 24 alex.thurgood 2006-08-02 07:59:51 UTC
@James
Server version 4.1.12 from memory, but I'll check and it's a remote server on a 
Linux machine. I'll sort out a create table statement and some sample data and 
post back here.

alex
Comment 25 jogi 2006-08-02 19:12:50 UTC
MACJOGI->TRA: Reproducable? Here not.
Comment 26 alex.thurgood 2006-08-07 14:20:17 UTC
mysql server version : 4.1.12
remote server on local LAN, accessed via IP address

MySQL JDBC connector : GA 5.03 or GA 3.1.12
Installed in : /Library/Java/Extensions/
Also separately tried : /Users/alex/

OOo versions : MacOSXPPC 2.0.3rc7, m178


Alex 
Comment 27 alex.thurgood 2006-08-07 14:26:06 UTC
Sample table structure :
CREATE TABLE citation (
citation_id int(11) unsigned zerofill NOT NULL auto_increment,
family_id int(11) NOT NULL default '0',
citation_ref varchar(100) NOT NULL default '',
majdate timestamp NOT NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP,
PRIMARY_KEY (citation_id)
)
ENGINE=MyISAM DEFAULT CHARSET=Latin1;

alex
Comment 28 alex.thurgood 2006-08-07 15:02:34 UTC
With GA 5.03 JDBC Connector, I can get this crash report from the Apple reporter :

Date/Time:      2006-08-07 12:22:24 +0200
OS Version:     10.3.9 (Build 7W98)
Report Version: 2

Command: droplet
Path:    /Applications/OpenOffice.org 2.0.app/Contents/MacOS/droplet
Version: ??? (???)
PID:     6869
Thread:  0

Exception:  EXC_BAD_ACCESS (0x0001)
Codes:      KERN_INVALID_ADDRESS (0x0001) at 0x900078b8

Thread 0 Crashed:
0   <<00000000>> 	0x900078b8 0 + 0x900078b8
1   <<00000000>> 	0x901c2258 0 + 0x901c2258
2   <<00000000>> 	0x901c69e4 0 + 0x901c69e4
3   <<00000000>> 	0x94729e10 0 + 0x94729e10
4   <<00000000>> 	0x9472ceb0 0 + 0x9472ceb0
5   <<00000000>> 	0x94740988 0 + 0x94740988
6   <<00000000>> 	0x947516a0 0 + 0x947516a0
7   com.apple.applescript 	0x761d6ff4 _ZN6Applet12ProcessEventEm + 0x44
8   com.apple.applescript 	0x761d5a74 _ZN6Applet4MainEv + 0x178
9   com.apple.applescript 	0x761d5d10 OSAAppletExecute + 0x3c
10  com.apple.applescript 	0x761d5e88 AppletComponent + 0xb0
11  <<00000000>> 	0x902b0e50 0 + 0x902b0e50
12  org.openoffice.script 	0x00002d38 0x1000 + 0x1d38
13  org.openoffice.script 	0x00002d78 0x1000 + 0x1d78
14  org.openoffice.script 	0x00002a38 0x1000 + 0x1a38
15  org.openoffice.script 	0x000028a8 0x1000 + 0x18a8

PPC Thread State:
  srr0: 0x900078b8 srr1: 0x4000d030                vrsave: 0x00000000
    cr: 0x24002422  xer: 0x20000004   lr: 0x90007438  ctr: 0x900078b0
    r0: 0xffffffe1   r1: 0xbffff290   r2: 0x00001203   r3: 0x00000000
    r4: 0x03000006   r5: 0x00000000   r6: 0x00000450   r7: 0x00001203
    r8: 0x00000000   r9: 0x00000000  r10: 0x00000000  r11: 0xa0004a78
   r12: 0x900078b0  r13: 0x00000000  r14: 0x00000000  r15: 0x00000001
   r16: 0x00000001  r17: 0x00000000  r18: 0xa01c1f20  r19: 0x00000000
   r20: 0x000036fb  r21: 0x00000000  r22: 0x00300f48  r23: 0x0000004d
   r24: 0xbffff350  r25: 0x00000450  r26: 0x00001203  r27: 0x00000000
   r28: 0x00000000  r29: 0x00000000  r30: 0x03000006  r31: 0x901c1f20

Binary Images Description:
    0x1000 -     0x2fff org.openoffice.script 	/Applications/OpenOffice.org
2.0.app/Contents/MacOS/droplet
   0x29000 -    0x29fff com.apple.applescript.component 1.9.3
/System/Library/Components/AppleScript.component/Contents/MacOS/AppleScript
   0xee000 -    0xeefff com.apple.osax.digihub 1.0
/System/Library/ScriptingAdditions/Digital Hub
Scripting.osax/Contents/MacOS/Digital Hub Scripting
 0x16ae000 -  0x16e0fff com.apple.osax.standardadditions 1.9.4 (???)
/System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/StandardAdditions
0x761d4000 - 0x76279fff com.apple.applescript 1.9.3
/System/Library/PrivateFrameworks/AppleScript.framework/Versions/A/AppleScript
0x87b40000 - 0x87b7bfff com.apple.AppleShareClientCore 1.3.2
/System/Library/Frameworks/AppleShareClientCore.framework/Versions/A/AppleShareClientCore
0x89ca0000 - 0x89cbcfff com.apple.AppleShareClient 1.3.2
/System/Library/Frameworks/AppleShareClient.framework/Versions/A/AppleShareClient
0x8fe00000 - 0x8fe4ffff dyld 	/usr/lib/dyld
Comment 29 alex.thurgood 2006-08-07 15:08:30 UTC
With 2.0.3rc7, JDBC Connector GA 3.1.12 :

Date/Time:      2006-08-07 12:22:24 +0200
OS Version:     10.3.9 (Build 7W98)
Report Version: 2

Command: droplet
Path:    /Applications/OpenOffice.org 2.0.app/Contents/MacOS/droplet
Version: ??? (???)
PID:     6869
Thread:  0

Exception:  EXC_BAD_ACCESS (0x0001)
Codes:      KERN_INVALID_ADDRESS (0x0001) at 0x900078b8

Thread 0 Crashed:
0   <<00000000>> 	0x900078b8 0 + 0x900078b8
1   <<00000000>> 	0x901c2258 0 + 0x901c2258
2   <<00000000>> 	0x901c69e4 0 + 0x901c69e4
3   <<00000000>> 	0x94729e10 0 + 0x94729e10
4   <<00000000>> 	0x9472ceb0 0 + 0x9472ceb0
5   <<00000000>> 	0x94740988 0 + 0x94740988
6   <<00000000>> 	0x947516a0 0 + 0x947516a0
7   com.apple.applescript 	0x761d6ff4 _ZN6Applet12ProcessEventEm + 0x44
8   com.apple.applescript 	0x761d5a74 _ZN6Applet4MainEv + 0x178
9   com.apple.applescript 	0x761d5d10 OSAAppletExecute + 0x3c
10  com.apple.applescript 	0x761d5e88 AppletComponent + 0xb0
11  <<00000000>> 	0x902b0e50 0 + 0x902b0e50
12  org.openoffice.script 	0x00002d38 0x1000 + 0x1d38
13  org.openoffice.script 	0x00002d78 0x1000 + 0x1d78
14  org.openoffice.script 	0x00002a38 0x1000 + 0x1a38
15  org.openoffice.script 	0x000028a8 0x1000 + 0x18a8

PPC Thread State:
  srr0: 0x900078b8 srr1: 0x4000d030                vrsave: 0x00000000
    cr: 0x24002422  xer: 0x20000004   lr: 0x90007438  ctr: 0x900078b0
    r0: 0xffffffe1   r1: 0xbffff290   r2: 0x00001203   r3: 0x00000000
    r4: 0x03000006   r5: 0x00000000   r6: 0x00000450   r7: 0x00001203
    r8: 0x00000000   r9: 0x00000000  r10: 0x00000000  r11: 0xa0004a78
   r12: 0x900078b0  r13: 0x00000000  r14: 0x00000000  r15: 0x00000001
   r16: 0x00000001  r17: 0x00000000  r18: 0xa01c1f20  r19: 0x00000000
   r20: 0x000036fb  r21: 0x00000000  r22: 0x00300f48  r23: 0x0000004d
   r24: 0xbffff350  r25: 0x00000450  r26: 0x00001203  r27: 0x00000000
   r28: 0x00000000  r29: 0x00000000  r30: 0x03000006  r31: 0x901c1f20

Binary Images Description:
    0x1000 -     0x2fff org.openoffice.script 	/Applications/OpenOffice.org
2.0.app/Contents/MacOS/droplet
   0x29000 -    0x29fff com.apple.applescript.component 1.9.3
/System/Library/Components/AppleScript.component/Contents/MacOS/AppleScript
   0xee000 -    0xeefff com.apple.osax.digihub 1.0
/System/Library/ScriptingAdditions/Digital Hub
Scripting.osax/Contents/MacOS/Digital Hub Scripting
 0x16ae000 -  0x16e0fff com.apple.osax.standardadditions 1.9.4 (???)
/System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/StandardAdditions
0x761d4000 - 0x76279fff com.apple.applescript 1.9.3
/System/Library/PrivateFrameworks/AppleScript.framework/Versions/A/AppleScript
0x87b40000 - 0x87b7bfff com.apple.AppleShareClientCore 1.3.2
/System/Library/Frameworks/AppleShareClientCore.framework/Versions/A/AppleShareClientCore
0x89ca0000 - 0x89cbcfff com.apple.AppleShareClient 1.3.2
/System/Library/Frameworks/AppleShareClient.framework/Versions/A/AppleShareClient
0x8fe00000 - 0x8fe4ffff dyld 	/usr/lib/dyld


Comment 30 alex.thurgood 2006-08-07 15:11:25 UTC
BTW, I have tried choosing different mysql table structures just incase it was a
driver problme. OOo still crashes when it comes to selecting the table to be
used in the mailmerge, even with simple varchar fields and an auto_increment
primary key field.
Comment 31 jjmckenzie 2006-08-07 15:12:30 UTC
@wurzel:

Thank you for the information.

@macjogi

Can you test this with the information given by wurzel?  Also, can you provide 
the test scenario you used.

James M.
Comment 32 jjmckenzie 2006-08-07 15:15:11 UTC
Issue definately exists but is not a showstopper (wurzel is only reporter) for 
2.0.3 release as database interface is not mature on Mac OS X version and this 
problem could not be reproduced by another person.  I do not have access to a 
Linux server with MySQL but will attempt to reproduce through a MySQL database 
installed on the same Mac OS X system.
James M.
Comment 33 jjmckenzie 2006-08-07 15:17:05 UTC
@amaze:

See issues 67712 and 67909 for Base wizards problems.  Is this what you were 
experiencing?

James M.
Comment 34 alex.thurgood 2006-08-07 15:48:58 UTC
@james

I might be the only qa reporter, but I have seen the same reports recently on 
the German users list, albeit without the in-depth explanations (so obviously 
taken with a word of caution). The functioning is however the same. You can 
connect to your mysql db, but then can not choose the table of your choice 
without OOo crashing.

One of the problems we have here is the very low numbers of people actually 
using OOo in productivity (and of course the summer hols don't help at the 
mo'). I'm going to ask if someone can reproduce on the French native lang 
lists, but it may also be a case of everyone being on holiday.

Alex

alex
Comment 35 jjmckenzie 2006-08-07 16:51:31 UTC
*** Issue 66158 has been marked as a duplicate of this issue. ***
Comment 36 jjmckenzie 2006-08-07 16:52:58 UTC
Issue 66158 is a duplicate of this issue as both deal with problems accessing 
MySQL databases through the JDBC connector.

I am in the process of testing whether or not the problem is with the JDBC or 
OpenOffice.org.

James M.
Comment 37 jjmckenzie 2006-08-07 18:21:50 UTC
@alex

I have installed MySQL as local to my Mac, installed the JDBC connector but I 
cannot 'see' the test database.  Are there any tricks to using the JDBC 
connecter from within OpenOffice.org?  BTW, I'm using the test database and I 
created a table called phonelist.

James M.
Comment 38 alex.thurgood 2006-08-07 23:03:44 UTC
@james : not any tricks that I can think of :-( 
The driver should be installed somewhere where Java and OOo can see it, and 
read it. I did this by copying the jar file to /Library/Java/Extensions (this 
is the place where Java extension libraries are classically stored), but you 
could always try your home directory. You need to tell OOo about the classpath, 
so in OOo you need to go to the Options - Java menu entry, wait for it to find 
your Java installation (which can take some time), and then click on the 
classpath button (third button down on the right of the dialog), click on add, 
and then navigate to the directory where you have put the driver and then 
select it and press OK. After that, you need to restart OOo (you may get a 
message telling you this, but it doesn't always display for some reason).


Upon restart of OOo :
I just used the db wizard to create a new mysql database document that chose 
the JDBC driver. This choice is actually suggested by the OOo database creation 
wizard. You get the opportunity to test the default provided driver class, 
which worked on my setup, and then on the next step you get to enter the 
parameters for accessing the mysql db. Since you have installed mysql locally, 
you should enter 127.0.0.1 or localhost as the name of the server, and then the 
name of the mysql db, which I assume in your case is test (you might have to 
try with Test, I'm not sure). Leave the default port of 3306 as it is. When you 
have filled these in, you can test the connection from that same dialog. Again, 
this should work. 

From memory, the test mysql db does not require a user password to be set, but 
that might have changed recently, I don't know, I always grant myself rights as 
a user on the mysql db to do the stuff that I need to do beforehand and then 
create my db and tables as I wish, so I hardly ever use the test db provided.

alex
Comment 39 jjmckenzie 2006-08-08 02:17:23 UTC
@alex:

Using MySQL 4.1.12 and the JDBC connector 3.1, I was able to create a test Mail
Merge document.  The problem may be that you are using a Beta connector that is
not compatible with OpenOffice.org 2.0.3.  

I am closing this issue as works for me. 

James M.
Comment 40 alex.thurgood 2006-08-08 06:21:27 UTC
@james : unfortunately, I don't agree that you have reproduced the scenario.

1) Your mysql server is internal to the machine on which you are carrying out 
the tests and not being remotely accessed.
2) I mentioned that I have used both the stable production 3.1.12 and the 
development 5.03 versions, and that even the stable failed to work.

From there being able to say that it works for you, well it's not the same 
setup, so it is hardly an honest comparison, is it ?

Alex
Comment 41 alex.thurgood 2006-08-08 18:19:49 UTC
Now testing with m180 PPC
Doesn't crash ;-), but still doesn't work, the wizard just gets stuck after
choosing the table and pressing OK. If you try to get a preview of the table,
you get an error message, saying "Illegal operation on empty result set" and an
empty window is displayed. You can not go on any further with the wizard, it is
stcuk at this stage.

I am including a LSOF we should really reopen the issue (assuming that this new
behaviour is now specific to Mac)

Alex
Comment 42 alex.thurgood 2006-08-08 18:21:59 UTC
Created attachment 38346 [details]
lsof when mailmerge wizard launched and selecting table in dialog
Comment 43 jjmckenzie 2006-08-09 05:25:35 UTC
Reopening issue to discuss issue further for troubleshooting.

This is definately NOT a showstopper for 2.0.3 but may be a configuration issue.

James M.
Comment 44 jjmckenzie 2006-08-09 05:31:44 UTC
@alex

I forgot one thing that I did.  I enabled Connection Pooling for my MySQL JDBC.

The steps I took were:

Tools -> Options.

In the Options dialog I went to OpenOffice Base, click on the Plus and then
Connections.  This will open a second dialog window.  Go to the
org.openoffice.comp.drive.MySQL.Driver and then enable connection pooling.  I
left the timeout at 60 seconds.  I have always used connection pooling for my
SQL connections and this comes from designing and developing EBJ for training
purposes.  Try this and let me know what happens.  I added a test Base database
for testing purposes and was also able to create a MailMerge document.

James M.
Comment 45 alex.thurgood 2006-08-09 08:23:09 UTC
@james : please bear in mind that I am now testing on m180. Version 2.0.3 just
crashed continuously, at least m180 doesn't crash straight away (but it does
still crash if you try and repeat table access 4 or 5 times). 

This means that I don't think detaching this issue from i65572 was the correct
thing to do, since it related to 2.0.3. Either we update this issue to point to
the latest version being tested (this isn't generally what we do on QA), or we
create a new issue pointing to the specific version being tested.

Connection pooling hasn't changed anything. In m180, I still can't get any
further with the mailmerge wizard dialog, even once I have selected a table and
made the fields correspond. The dialog just sits there, and all I can do is
either "Cancel" or click on the "Previous" button.

Alex
Comment 46 alex.thurgood 2006-12-05 12:02:33 UTC
BTW, rc2 for PPC isn't up yet, so I can't test for that version

alex
Comment 47 jjmckenzie 2006-12-30 05:24:56 UTC
@wurzel:

I am trying to locate a Mac Intel built ODBC for MySQL.  When found I will
advise through the mac@posting mail list as to its location and add it to this
issue, if this is allowed.

James McKenzie
Comment 48 jjmckenzie 2006-12-30 05:27:06 UTC
*** Issue 66146 has been marked as a duplicate of this issue. ***
Comment 49 jjmckenzie 2006-12-31 03:17:43 UTC
Attempted to use MySQL ODBC driver for the Mac Intel platform and received an
error about a missing dynamic library, libodbc.2.1.10.dylib in /usr/lib.

James McKenzie
Comment 50 Frank Schönheit 2007-07-03 09:14:56 UTC
resetting target
Comment 51 alex.thurgood 2008-05-09 18:39:56 UTC
This now works for me in OOo Aqua Beta 3.0 m3. Setting to resolved, WFM.

Alex
Comment 52 alex.thurgood 2008-05-10 21:43:14 UTC
Closing