Alexander Thurgood wrote:
Le 26/05/12 22:30, Girvin R. Herr a écrit :
Hi Girvin,
If you have links to LO/OOo configuration documentation for ODBC
connection to MySQL, I would be willing to try it.
Thanks.
I wrote a tutorial for this very purpose many years ago for OOo, but it
would equally apply to LO today, things really haven't changed that much
(if at all) insofar as getting ODBC connections set up are concerned. I
can't actually find my English version at the moment, only the French
one I wrote, but note that John McCreesh also provided one that is still
available here :
http://www.unixodbc.org/doc/OOoMySQL9.pdf
Alex
Alex,
Thanks for replying with this valuable information. I printed the
document and I will try it sometime. It is always good to have a backup
solution.
I don't think my problem is with Java. The main reason is that I am
using the same database query to get my data with Oracle Report Builder
(ORB) and with Calc import. The Calc import runs at a reasonable speed,
about 15 seconds or less for about 1800 records, where ORB takes over an
hour to process the same data. I think the problem is definitely with
the ORB interfaces. Yesterday, under this subject, I posted additional
LO/ORB error data from tests I ran. Today, I want to go back to
OpenOffice 3.3 and run the same tests to see if OOo/ORB produces the
same errors and runs slow. I have used ORB with OOo 3.3 in the past
and, as I remember it, although it wasn't fast, it didn't take nearly as
long as this LO/ORB takes. If the OOo 3.3 tests are not as slow, then
that indicates there may be something wrong with the ORB bundled with
LO. I will have to do more work in that area to try to narrow it down.
Thanks again for your help.
Girvin
--
For unsubscribe instructions e-mail to: [email protected]
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
