Conflicting security behavior between InfoPath and IE

  • Thread starter Gregs List Acct
  • Start date
G

Gregs List Acct

I *thought* that security settings would behave identically between IE and
InfoPath with regard to ActiveX objects, but I was wrong.

I'm using the ActiveX object "WScript.Network" to obtain a user's domain and
alias. I could create this object on an HTML page and make calls within IE,
but my InfoPath form would error using the same code. I had to change the
security setting for "Initialize and script ActiveX controls not marked as
safe" to "Enable" in order for the InfoPath form to call the code without
error.

Does anyone know why there is a discrepancy in behaviour between IE and
InfoPath?
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top