Apache OpenOffice (AOO) Bugzilla – Issue 54783
I/O error when using macros within documents or when editing paths
Last modified: 2007-02-05 13:33:21 UTC
We're using OOo Beta2 as test environment in our company. We're using base as frontend for a MySQL server. As enlargement for the standard functions the form owns several basic macros. For the use of these macros for different users, there's a "basic" folder on one server. The users access via network on the data on this server. Changing the basic path to the folder on the net-device and a simultanously deactivation of the default paths causes an I/O error. Only when the macros are copied into the default path for basic macros, they work again. Additionally, I receive an I/O error, when I try to integrate the macros in the form (= writer document in base) (the marcros aren't locally safed). Only, when I delete all macros integrated in the document, the error message disappears.
change component to scripting because this has nothing to do with database. The basic path and libraries settings are not working in general.
Confirmed. Quick reproduction: 1. Open Tools/Options->OpenOffice.org/Paths 2. Delete the user-Path from the BASIC-Paths 3. Add a custom path (any other valid directory) 4. Try to create a new macro -> Error loading BASIC of Document ... This is just one of the countless occurrences of this error :-( Note for myself (might result in other tasks): If you copy the entire content of .OpenOffice.org/usr/basic/Standard to a custom path and change the default path to that directory the scripts will never be found. Additionally it appears as if we require a restart of the application after changing the path. jsk->ab: I believe TBE is still on vacation so i reassign the issue to you.
Changing Basic paths is not supported any more and cannot be reimplemented easily. So in the future the Basic paths won't be editable any more in Tools/Options. This is covered by issue 27436 currently set to OOo later. But according to pb issue i27436 is very easy to fix, so maybe it should be set to OOo 2.0.1 as this one definitely is WONTFIX for now.
*** Issue 54600 has been marked as a duplicate of this issue. ***
going to close ancient issues
closing ancient issues