Thanks Jim for introducing this topic.
A small company I know is using an ACCESS DB with macros exporting certain information into EXCEL
spreadsheets. This ACCESS DB is currently preventing the company to change over from MSO to LibO
A 2 step approach is discussed: First to migrate from MSO to LibO using W7 and second moving from
Windows to Linux. (Distributions not yet decided but most likely Linux Mint of Linux Mint Debian or
Therefore, 1 more question from my side: Assuming that using Access2Base helps us to get the DB and
the macros into Base and create the Calc spreadsheets, can this BASE DB with the LibO macros be used
as they are when changing from W7 to Linux?
On 2014-08-11 06:47, Jim Byrnes wrote:
I am still using the 3.xx version of LO that came with Ubuntu 12.04 and haven't been on the main
LibreOffice site for some time. I've been reading the naming discussion (Fresh/Still etc) and
decided to look at the site. While there I stumbled across Acces2Base. I've always thought
writing macros in LO was way harder than it should be because of UNO, so this is an interesting
A couple of questions:
(1) Has anyone here used it and does it make writing macros for Base easier?
(2) I write most of my macros for Calc so is there a Excel2Calc planned?
To unsubscribe e-mail to: email@example.com
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
Impressum (Legal Info)
: 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