----- Original Message -----
From: "William W. Austin" <[email protected]>
To: <[email protected]>
Sent: Tuesday, April 17, 2007 9:16 PM
Subject: [discuss] MyODBC -> OOo base connectivity question on fedora linux
fc 6
I am running fedora fc 6 on an x86_64 (dual core athlon) box and am having
problems connecting with a mysql database.
Previously (IIRC over a year ago) I had this working on an i386 box (fc3
or 4 - I forget which), but with the x86_64 box. I am having problems.
I can connect to the database, but for instance as soon as I select a
table, I get a crash. There is no core dump that I can find - only the
screen which says to paste the info into the bug report. The results are
the same for form creation - I can (apparently) successfully "create" a
blank form and the (empty) rows are shown on it; however, as soon as I
try to access any data, I get the same crash.
At first I thought the problem was most likely a mismatch - I was running
an x86_64 version of mysql and only a 32-bit version of OOo. So I
removed 2.2 (temporarily) and re-installed the latest official update for
fc 6 and recomiled an x86_64 version of MyODBC, putting everything in one
architecture.
The results are unchanged.
Before I file the bug report I'd like to track this down a bit further
(and maybe find a solution, too) so any pointers on this one would be
very greatly appreciated.
Also, please feel free to write me off-list (or at least please CC me).
An over-zealous spam filter with my ISP has been "eating" posts in
several mailing lists of late, although email cc'ed or addressed directly
to me seem to get through without problems (yes, even spam ... sigh).
Thanks,
--
william w. austin [email protected]
"life is just another phase i'm going through. this time, anyway ..."
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
