|
Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
| Summary: | No more VBA support | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Calc | Reporter: | niederbayern <eva-email> | ||||
| Component: | programming | Assignee: | issues@vba <issues> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | issues@sc <issues> | ||||
| Severity: | Trivial | ||||||
| Priority: | P2 | CC: | issues, mechtilde, stx123 | ||||
| Version: | DEV300m14 | Keywords: | oooqa, regression, release_blocker | ||||
| Target Milestone: | --- | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Issue Type: | DEFECT | Latest Confirmation in: | --- | ||||
| Developer Difficulty: | --- | ||||||
| Attachments: |
|
||||||
|
Description
niederbayern
2008-06-03 21:33:08 UTC
Created attachment 54220 [details]
spreadsheet document containing VBA macro
add to CC I change component It seems vba is not a valid one 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 http://go-oo.org/download/ 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. 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 @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. 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 line URE_MORE_TYPES=$ORIGIN/offapi.rdb ${${$ORIGIN/unorc:PKG_SharedUnoFile}:UNO_TYPES} ${${$ORIGIN/unorc:PKG_UserUnoFile}:UNO_TYPES to URE_MORE_TYPES=$ORIGIN/offapi.rdb $ORIGIN/oovbaapi.rdb ${${$ORIGIN/unorc:PKG_SharedUnoFile}:UNO_TYPES} ${${$ORIGIN/unorc:PKG_UserUnoFile}:UNO_TYPES *** This issue has been marked as a duplicate of 88739 *** closed duplicate |