Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 7 Feb 2001 12:09:31 +0100 (CET)
From:      "O. Hartmann" <ohartman@ipamzlx.physik.uni-mainz.de>
To:        freebsd-database@freebsd.org
Subject:   FreeBSD/MySQL/ODBC/StarOffice (fwd)
Message-ID:  <Pine.BSF.4.21.0102071209210.8799-100000@ipamzlx.physik.uni-mainz.de>

next in thread | raw e-mail | index | archive | help


--
MfG 
O. Hartmann

ohartman@mail.physik.uni-mainz.de
----------------------------------------------------------------
IT-Administration des Institut fuer Physik der Atmosphaere (IPA)
----------------------------------------------------------------
Johannes Gutenberg Universitaet Mainz
Becherweg 21
55099 Mainz

Tel: +496131/3924662 (Maschinensaal)
Tel: +496131/3924144
FAX: +496131/3923532

---------- Forwarded message ----------
Date: Wed, 7 Feb 2001 12:08:34 +0100 (CET)
From: O. Hartmann <ohartman@ipamzlx.physik.uni-mainz.de>
To: freebsd-database@freebsd
Subject: FreeBSD/MySQL/ODBC/StarOffice

Dear Sirs.
Again I must ask the community because of problems with some
standards I can not solve.

The system's facts: 

FreeBSD 4.2 based server machine, running the recent version of MySQL
server.

A bunch of FreeBSD clients using StarOffice 5.2 (german) and a bunch of
Windooze PCs running Win2000 and StarOffice 5.2 and Office 2000.
On the Windooze clients I use MyODBC 2.50.36 as ODBC driver with some
problems under StarOffice (using varchar(255) truncates in StarOffice
inputs to 8 characters ... but inputs made by hand (mysql-client) are
shown in the correctly length). Access has no problems.

We want to use more UNIX systems, so we install FreeBSD clients and use
StarOffice (Linux emulation). We also have several Linux boxes using also
StarOffice.

On Linux and FreeBSD I compiled the sources for MyODBC 2.50.36 either with
iODBC or unixODBC. Search path for the system wide configuration is in both
cases /usr/local/etc. For each user using StarOffice in conjunction with the
MySQL server we installed an additional .odbc.ini in their homes. So far,
this was done on Linux AND FreeBSD.

When trying to use an ODBC database out of StarOffice, I can not use ODBC
under Linux or FreeBSD. It's always the same error. Under FreeBSD, I try 
to list all ODBC databases, but this implies that .odbc.ini, /usr/local/etc/odbcinst.ini
and /usr/local/etc/odbc.ini has been properly read by StarOffice. StarOffice 
reports an error and tells me to check my installation/configuration against
libodbc.ini. For that, I made some usefull and some senseless links to the
existing libraries, to reflect the existence of libodbc.so. Without
success. The first time, I try to connect I get this error, all succeeding errors
are about to check file ".". The same problem is under Linux, so I think this is not
a kind of "Linux vs. FreeBSD compiled libraries of MyODBC". It is a more sophisticated
problem how StarOffice reads the proper information.

Does anyone did the task successfuly?
If you would do this job, what aspects are to be aware of? Any hints, tips?

Thanks a lot ... 


Oliver

--
MfG 
O. Hartmann

ohartman@mail.physik.uni-mainz.de
----------------------------------------------------------------
IT-Administration des Institut fuer Physik der Atmosphaere (IPA)
----------------------------------------------------------------
Johannes Gutenberg Universitaet Mainz
Becherweg 21
55099 Mainz

Tel: +496131/3924662 (Maschinensaal)
Tel: +496131/3924144
FAX: +496131/3923532




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-database" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0102071209210.8799-100000>