Issue 90326 - No more VBA support
Summary: No more VBA support
Status: CLOSED DUPLICATE of issue 88739
Alias: None
Product: Calc
Classification: Application
Component: programming (show other issues)
Version: DEV300m14
Hardware: All All
: P2 Trivial (vote)
Target Milestone: ---
Assignee: issues@vba
QA Contact: issues@sc
Keywords: oooqa, regression, release_blocker
Depends on:
Reported: 2008-06-03 21:33 UTC by niederbayern
Modified: 2013-08-07 15:15 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

spreadsheet document containing VBA macro (11.89 KB, application/vnd.oasis.opendocument.spreadsheet)
2008-06-03 21:34 UTC, niederbayern
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description niederbayern 2008-06-03 21:33:08 UTC
VBA macro can not be executed in OOo DEV300m14. It ends up i a runtime error.
Same macro can be executed with OOo 2.4.0 and 2.4.1rc2, all builds from Sun.

Please try the attached Calc document, that contains a VBA macro. Just click on
"Start Demo".
Comment 1 niederbayern 2008-06-03 21:34:17 UTC
Created attachment 54220 [details]
spreadsheet document containing VBA macro
Comment 2 Mechtilde 2008-06-03 21:40:39 UTC
add to CC
Comment 3 Mechtilde 2008-06-04 06:53:41 UTC
I change component

It seems vba is not a valid one
Comment 4 noel.power 2008-06-04 10:42:05 UTC
It seems that there was a decision ( not by me, and I did object ) to disable
import and running of VBA code by default for Sun builds. It seems we disagree,
the 'powers that be' think because this ( the VBA interop feature ) is an
incomplete feature that it should be disabled by default. IMO all interop
features ( e.g. the Microsoft filters, vba interop etc ) are by their nature
incomplete, they will *never* be complete. The best you can hope for is to
identify and concentrate on the areas that are used most and/or are most
important to users. The Microsoft filters have been around for a long time and
have had the benefit of many years of useful feedback to determine their
development roadmap. It seems that for vba interop this opportunity is sadly
being denied

Note: vba will remain on by default in the builds from ooo-build If you want to try those e.g. for 3.0 builds look for
the unstable section at the bottom of the page from the link above.
Comment 5 noel.power 2008-06-04 10:47:15 UTC
I forgot to mention, to re-enable the vba import goto 

Tools | Options | Load/Save | VBA Properties | Exectuteable code

and select the Exe.. Code checkbox
Comment 6 niederbayern 2008-06-04 11:48:11 UTC
@npower: Please note that this is NOT an issue about importing VBA-Code, but
this is an issue about executing VBA-Code!

Execution of VBA-Code in 3.0 ist not possible, no matter if "Tools | Options |
Load/Save | VBA Properties | Exectuteable code" is checked or not.

Comment 7 noel.power 2008-06-04 12:42:27 UTC
This looks to me like a duplicate of issue 88739, its marked as fixed but it's
not clear whether this fix is actually integrated yet. I left a question about
that in the the issue mentioned.

in the mean time you could manually tweak the
ooo-dev/basis3.0/program/fundamentalbasisrc file and change the 


URE_MORE_TYPES=$ORIGIN/offapi.rdb $ORIGIN/oovbaapi.rdb

*** This issue has been marked as a duplicate of 88739 ***
Comment 8 Mechtilde 2008-06-04 13:49:38 UTC
closed duplicate