Hi,
I have created a spreadsheet that contains a UserForm and in that userform I have added a Microsoft Spreadsheet Control Object(open the control toolbox, right click and then select Add Additional Controls and select MicroSoft Spreadsheet Control). This object is basically a little spreadsheet that goes in the Form.
There is, however, a problem: for each execution of the program the first time that that user form is utilized, the user is presented with a popup window saying "This application is about to initialize ActiveX controls that might be unsafe. If you trust the source of this file, select OK and the controls will be initialized using your current workspace settings."
I really don't want this to popup in my commercial application. Is there some way to prevent this from happening, for example by making the Spreadsheet a trusted source? (It would be nice if the Macro warning doesn't popup either when the application starts)
ps. I don't want the macro security level to be set to low, but even setting it to low doesn't prevent the activex warning.
Thanks,
Taylour
I have created a spreadsheet that contains a UserForm and in that userform I have added a Microsoft Spreadsheet Control Object(open the control toolbox, right click and then select Add Additional Controls and select MicroSoft Spreadsheet Control). This object is basically a little spreadsheet that goes in the Form.
There is, however, a problem: for each execution of the program the first time that that user form is utilized, the user is presented with a popup window saying "This application is about to initialize ActiveX controls that might be unsafe. If you trust the source of this file, select OK and the controls will be initialized using your current workspace settings."
I really don't want this to popup in my commercial application. Is there some way to prevent this from happening, for example by making the Spreadsheet a trusted source? (It would be nice if the Macro warning doesn't popup either when the application starts)
ps. I don't want the macro security level to be set to low, but even setting it to low doesn't prevent the activex warning.
Thanks,
Taylour