Hi,
My addin registers for the WorkbookOpen event and when this event gets
called it accesses some properties of ActiveX controls in the workbook. The
problem is that WorkbookOpen gets called before the user has closed the
ActiveX control security warning. If I access the ActiveX controls before
this message box is closed Excel will throw an exception. After the message
box is closed the code works fine.
Does anybody know how to wait until the user has closed that message box?

Thanks

Hans Merkl

Hi,

Thanks for your input.
What is the exactly error msg you got?
Office Application is STA application.
You may try to call the Sleep method(API in VBA or Thread.Sleep in .NET),
but that will stop whole Office Thread.

I think we should dedicate how to dismiss the error dialog.

What ActiveX control are you using?
Have you tried to use the Windows MediaPlayer ActiveX control?



Best regards,

Peter Huang
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.

Hi Peter,
It turns out we had a timer event set up in Excel. As soon as this timer
gets triggered the WorkbookOpen event gets called even if the user hasn't
closed the ActiveX warning yet. After disabling the timer everything is
working fine.

I guess this could be viewed as a bug in Excel.

Hans



On Wed, 08 Mar 2006 08:01:18 GMT, "Peter Huang" [MSFT] wrote:

Hi,

Thanks for your input.
What is the exactly error msg you got?
Office Application is STA application.
You may try to call the Sleep method(API in VBA or Thread.Sleep in .NET),
but that will stop whole Office Thread.

I think we should dedicate how to dismiss the error dialog.

What ActiveX control are you using?
Have you tried to use the Windows MediaPlayer ActiveX control?



Best regards,

Peter Huang
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.

Hi Max,

Thanks for you update!
And I am glad that you have resolved the issue.
So far without detailed troubleshooting and debugging it is hard to confirm
if this is a problem in the Excel product.
I do understand your concern in this scenario, I highly suggest you can
submit this feedback to our product feedback center:
http://lab.msdn.microsoft.com/produc...k/default.aspx

Thanks for your understanding!

Best regards,

Peter Huang
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.