https://issues.apache.org/ooo/show_bug.cgi?id=118821
Ariel Constenla-Haile <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #7 from Ariel Constenla-Haile <[email protected]> 2012-01-23 12:11:55 UTC --- (In reply to comment #4) > Hi Oliver > > the issue is that the "oleautobridge.uno.dll" is *missing* > in the installation set. Adding "oleautobridge.uno.dll" > and registering it solves the problem. it seems Oliver-Rainer is building with --disable-atl @Oliver-Rainer: can you confirm? > imho this has nothing todo with windows registry system integration. > please add "oleautobridge.uno.dll" and registration into dev builds. even if the DevSnap is build with ATL support, you cannot click a VB script on the Explorer and execute, because the DevSnap installer does not register any activex component. > - open aoo and check with macro: > > OPTION EXPLICIT > Sub Test > Dim oManager as Object > oManager = CreateObject("com.sun.star.ServiceManager") > MsgBox isNull(oManager) > End Sub In a DevSnap with ATL enabled, and so with the UNO component, but with all system integration from other OOo standard versions (I removed all of them, I only have the DevSnapshot installed), I can not run this macro, nor execute a VB script outside AOO. Do you have by chance another OOo/AOO installation with the ActiveX component registered? You can test this by double-clicking on the explorer on any VB script with AOO code. -- Configure bugmail: https://issues.apache.org/ooo/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
