For Programmers: Free Programming Magazines  


Home > Archive > Visual Basic > November 2005 > Re: An ActiveX control might be unsafe to interact with other parts of the page. Do y









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author Re: An ActiveX control might be unsafe to interact with other parts of the page. Do y
fniles

2005-11-29, 6:55 pm

Thanks for your help.
I found my problem.
From Project Properties, I need to change the Startup Object to Sub Main to
execute the Sub Main.

Sub Main()
m_fSafeForScripting = True
m_fSafeForInitializing = True
End Sub


"Igor Tandetnik" <itandetnik@mvps.org> wrote in message
news:eROzwwe8FHA.3044@TK2MSFTNGP10.phx.gbl...
> "fniles" <fniles@pfmail.com> wrote in message
> news:eGgB2re8FHA.636@TK2MSFTNGP10.phx.gbl
>
> I don't really know VB so I cannot intelligently comment on this code.
> Just make sure that pdwEnabledOptions does indeed end up with
> INTERFACESAFE_FOR_UNTRUSTED_CALLER flag in it. If I were you, I'd just
> throw in both INTERFACESAFE_FOR_UNTRUSTED_CALLER and
> INTERFACESAFE_FOR_UNTRUSTED_DATA unconditionally. It is very unusual to
> have to vary your flags depending on the IID parameter.
> SetInterfaceSafetyOptions is also only needed in rare advanced cases -
> most of the time you just return S_OK and do nothing.
> --
> With best wishes,
> Igor Tandetnik
>
> With sufficient thrust, pigs fly just fine. However, this is not
> necessarily a good idea. It is hard to be sure where they are going to
> land, and it could be dangerous sitting under them as they fly
> overhead. -- RFC 1925
>



Sponsored Links







Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive

Copyright 2008 codecomments.com