Home

Macro

Paths

Insert Data

Example 1

Example 2

Blog

Evaluation of GnuCash Data in OpenOffice.org

How to fetch the macro and where to store it

This is free open source software under GPL license, you use it at your own risk.
If you have not done so already, please read and understand the Limitations and Preconditions. Malfunction and misunderstandings are bound to happen if you do not.

If your OpenOffice.org Version is not 3.0.0 you should install the macro as a regular extension from OOo's extension repository. An installation as an extension will enable you to take advantage of the Online-Update of the Extension Manager in the future, i.e. bug-fixes and improvements of the macro will be delivered to you half-automatically. You will still have the choice if you want to install the new version or not, but you will know there is a new one available.

Version 2.x or 3.0.1 and later:

Download the extension - i.e. the file "gnuc2ooo.oxt" - from my project page and install it using the Extension Manager under Tools → Extension Manager.
If there is only one user on your system it will be sufficient to install it under "My Extensions".
If there are several users you may also install it as a shared extension under "OpenOffice.org Extensions" but then the process running OpenOffice will need administration rights - under ubuntu that means that it has to be started at the terminal window with "sudo soffice" (The configuration of the macro will still be user-specific - each user will read his own GnuCash data and store the output into his own Base-database).
If, on installing "gnuc2ooo.oxt" through the extension manager you get the following error:"Failed to register package for vnd.sun.star.expand.$UNO_USER_PACKAGES_CACHE/uno_packages/Bdxk6D_/gnuc2ooo.oxt/python/", it might be because the binding Python-Uno of the python language to OOo is lacking. Get package "python-uno" from your usual sources.
If you install " gnuc2ooo.oxt" on unix platforms via OOo extension manager into the "OpenOffice.org Extensions" directory (as opposed to the "My Extensions" directory), in the same OOo-session you will get a namelesse node in "Run macros" of the macro tree. This is harmless since the problem is fixed after the next restart of OpenOffice.
The project page of my extension can be found at http://extensions.services.openoffice.org/project/gnuc2ooo.

Version 3.0.0:

Under version 3.0.0, however, you will have to store the macro manually and you will have to store it as a shared OpenOffice.org Macro as there is a bug in this version that keeps it from recognizing user-specific python-macros.
The sourcetext of the macro can be downloaded from
here (hosted by BerliOS Logo ).
It must be stored under the name of gnuc2ooo.py into the directory for shared OpenOffice.org macros:
On Windows this is "
C:\Program Files\OpenOffice.org 3\Basis\share\Scripts\python".
In ubuntu it is "/usr/lib/openoffice/share/Scripts/python".
In case the directory ....python does not exist (but only the superior Path up to ...Scripts): please create a subdirectory „python“.


Review of results:

Please select the following menupath out of an arbitrary application in OpenOffice.org: Tools → Macros → Run Macro.
If you activate in addition the plus-sign left from "OpenOffice.org Macros" resp. "My Macros" and then select "gnuc2ooo" a window like this will be displayed provided that everything went well:

When installing through Extension Manager there will be an additional directory-node "gnuc2ooo.oxt" - doesn't make any difference.

Next step: configure paths, create database