To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=90326
------- Additional comments from [EMAIL PROTECTED] Wed Jun 4 09:42:05 +0000 2008 ------- 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. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
