With macros i think the problem is that MS uses a different language for macros and their macros
keep being used as an attack vector for malware. So, all sorts of ways have had to be built to
prevent macros from executing whenever they want.
Sadly, LibreOffice uses a different version of Basic that doesn't seem to have had security issues "out
in the wild" (afaik). A
couple of times people have been urged to upgrade to new branches to
avoid known issues that were fixed in the newer branch but that was almost entirely preventative
rather than reactive. I think LibreOffice even allows a few other languages to be used, such as
So, if people write macros using the language(s) that LibreOffice uses then presumably those
macros don't have to be imported/converted?
Sorry i don't know any of this from 1st hand experience but just have my opinions built-up from the
many posts on the Users List about these topics so i could easily have misunderstood things.
From: Rodrigo Bigo <firstname.lastname@example.org>
To: email@example.com; firstname.lastname@example.org
Sent: Friday, 6 September 2013, 13:08
Subject: [libreoffice-users] Suggestions: Sorry but the feedback page is not working, I am sending
Sorry but the feedback page is not working, I am sending by email
I downloaded the package LibreOffice, because I am currently the a Visual
Basic and MsAccess programmer.
And I thought a very good tool, however I would like to send some
The suggestions are:
1 - Password Option to prevent the drawing mode for end users, objects from
the database as Forms, Tables, Reports, and Macros
2 - Option to start creating a form that would be a menu option to open
other forms, views, tables, queries and reports.
3 - Boot Options to a database, with the ability to more easily hide the
toolbars and menus.
End users are not familiar with many tools and buttons. And they need ease
and simplicity to be able to use a program.
4 - To have to import macros, and ask the password protection code,
discourages programmers to distribute databases for end-users and even by
the internet. Ideally macros not needed to be imported, and they would only
be allocated in a sub-folder of the archive database.
If these options could be implemented, surely this would stimulate much
MsAccess programmers to migrate to LibreOfficeBase.
Rodrigo Bigo Jr
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