Peter Eberlein wrote: > Hi, > > we want to restrict the use of the Basic IDE, but because of a missing > error handling in OpenOffice's macros, it is simple to produce an error > and to access the IDE (e.g. bind the macro > Depot.Depot.AddShortCuttoControl() to a field, a frame, a graphic). > > The only way I see is to manipulate the script.xlc (not safe, the user > can overwrite this) or to delete the macros from the shared folder. > > Any other ideas how to avoid this? > IMO the correct approach would be over the security settings, but these > are only for document macros.
Macro security is about macro execution, not about availability of the BasicIDE. I think the correct way to fix your problem would be to change the BasicErrorHandler and make its behavior dependant on a configuration setting. Ciao, Mathias -- Mathias Bauer (mba) - Project Lead OpenOffice.org Writer OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't reply to "[EMAIL PROTECTED]". I use it for the OOo lists and only rarely read other mails sent to it. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
