Embedded OCX unsafe
We would like to include the Microsoft MSCOMCTL2.OCX file to enable us to use the Date Controls. We have embedded this control in our web page and it downloads to a client pc. However when we want to use the control, an error message appears that say it is an unsafe control. How do we go about solving this problem.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Tom,
Your comment is 100% correct this is how we achieved the workaround, however we can't supply this web app to our clients asking them to change their settings. Is there no other workaround ?
Your comment is 100% correct this is how we achieved the workaround, however we can't supply this web app to our clients asking them to change their settings. Is there no other workaround ?
ASKER
Adjusted points to 500
dtd:
We have not found any, nor has M$ cooperated in finding a solution (although, to be honest, we have not really pushed them on it).
Cisk is right, however. Once these settings are established and implemented once, the problem should go away forever(?). The two issues that I find problematic is convincing customers/clients that it is alright to lower security for your specific site, and the possibility that they may already have a "standard" for security in the trusted zone which does not allow for your modifications.
I must say, it seems odd to me that Microsoft would put out controls that do this. In our case, it was not any of OUR controls that were causing this. Rather, it was "implicit" controls being called by the application.
Oh well...
Wish I could be more positive.
Tom
We have not found any, nor has M$ cooperated in finding a solution (although, to be honest, we have not really pushed them on it).
Cisk is right, however. Once these settings are established and implemented once, the problem should go away forever(?). The two issues that I find problematic is convincing customers/clients that it is alright to lower security for your specific site, and the possibility that they may already have a "standard" for security in the trusted zone which does not allow for your modifications.
I must say, it seems odd to me that Microsoft would put out controls that do this. In our case, it was not any of OUR controls that were causing this. Rather, it was "implicit" controls being called by the application.
Oh well...
Wish I could be more positive.
Tom
Seems to me we had pretty much the same issue, and, for some reason, Microsoft has created and distributed controls which it does not identify as "safe" for scripting. IE 5 all of a sudden started popping these errors where IE 4 had no problem.
Tom