Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index

On 02/12/2013 01:34 AM, e-letter wrote:
On 11/02/2013, todd.e.moore <> wrote:
Originally I posted under my
account.Unfortunately, I need the macros enabled.  The spreadsheet is
developed by another company and includes features/functions that we must
use to properly submit requests.The behavior I observe is that after
changing security settings to allow the macros to run, I receive a macro
execution error that pops up on the screen.  Clicking on the equivalent of
"ok", "ignore", "cancel" just displays another error message.  This
continues for what seems about 30 clicks.  Then the boxes no longer appear.

Trying to do anything in the UI, even closing the file, starts the error
message deluge again.I noticed the issue in v3.x.x and hoped that with
v4.0.0 there may have been changes that would cope with the macros in this
file.  Unfortunately, the problems persist.Attaching file (1MB zip file
containing a single MS Excel ) that causes this issue to occur.

Amazed that a private company receives a proprietary file from another
private company and asks the libre software community to solve a
proprietary problem.

LO is not an m$ clone. A business that can't afford to pay m$
licences, most probably shouldn't be in business.

How does odf benefit from LO being used to solve your problem?

Have you contacted the source of the document and asked them to
re-format the document to ods?

What did they say? ;)

Have you contacted m$ and asked them to make their software easier to
use with non-m$ products? Did you get a reply ? ;)

How much company time have you wasted, compared to the cost of buying
a legitimate copy of m$? Is your MD aware?


The issue is macro conversion which is tricky at best. As budgets tighten many are looking for less expensive or free options for software and these issues are important to address in a polite manner not snide comments about the validity of their license or how they should use MSO. MS does not by their choice have versions of MSO for all OSes so depending on your OS you may not even have an option to use MSO.

In previous post, it was noted that the macro may be buggy because it apparently does not always run correctly in Excel (2003). So there may have two independent problems: a buggy macro and macro conversion/interoperability.

Macros are the hardest area to convert because of differences in the APIs between MSO and LO.

Jay Lozier

For unsubscribe instructions e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.