On 02/15/2013 01:59 PM, Heinrich Stoellinger wrote:
Hello,
I know I have gone on about the native connector before. My situtation
is like this at the moment:
- it works like a charm on 4.0.0.3 running Debian-Wheezy
- it neither works on Mint-Nadia or Windows-Vista (I know, I know --
I should upgrade THAT system!). The connector DID however work under
Vista and LO 3.6.5.
Unfortunately I really don't have the time to compile it myself...
What are the plans in any case?
Regards
H.S.
One of the problems depends upon whether the OS is 32 bit or 64
bit. I have a tower that is 64 bit and a MacBook which uses 32 bit with
both using Ubuntu 12.04 LTS. The native connector works fine for 64 bit
but does not work for the 32 bit. MySQL also has a JDBC driver on their
website that works quite well for 32 bit Ubuntu. This has been the case
since LO 3.5.7 if not before. (I download all of my LibreOffice files
from the ODF website.)
If I remember correctly, keeping the native connector current as
new versions of LO required more time than the developer of the
extension had available.
--Dan
--
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
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
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.