R
rasx
<p align=left>Dear InfoPath Team: </p> <p align=left>
When I open an InfoPath form connected to a SQL Server database via an
Office Data Connection (ODC) I get annoying security warning messages. The
assumption here is that the ADO 2.8 security settings are NOT configurable by
developers. It appears the a solution is to explore signing forms or “fully
trusting†forms—or using a web service (preferably with ADO.NET datasets—an
implied recommendation based on a <a
href="http://msevents.microsoft.com/cui/W...lture=en-us&EventID=1032259551&CountryCode=US">recent
InfoPath webcast</a>). I even saw posts in the <a
href="http://msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.infopath">InfoPath
MSDN discussion group</a> about this matter but only sketches about setting
Internet Explorer security levels were suggested by someone <em>not</em> from
Microsoft.
</p>
<p align=left>Please see the images attached to the <a
href="http://spaces.msn.com/members/rasx/Blog/cns!1ptAuj6tD_zAu_dIRM-HCKaA!134.entry">Blog
entry version</a> of this post to view the error messages. I clearly
irritated <a
href="http://www.franklins.net/fnetdotnetrocks/dotnetrocks.aspx?showid=95">Bernard
Wong</a> at a 2004 MSDN event in Burbank when I showed him these error
messages. I just lifted up my laptop and mumbled something and showed him the
error message on my screen. He immediately said, “I’m not a mind reader!†and
did not answer the question. I did not need him to read my mind. I just
needed an expert to recognize that these error messages came from someone
somewhere at Microsoft. We need to explore the possibility that these
messages pop up for a reason and not the possibilities surrounding my nascent
clairvoyance. </p> <p align=left>I cannot be the only person on the entire
planet that saw these error messages. There must be at least one other person
who knows about these messages: the original author of the messages. Let us
begin a global search for this person (or persons) before we look for
extra-terrestrial life. I just thought I’d start with the InfoPath team. </p>
When I open an InfoPath form connected to a SQL Server database via an
Office Data Connection (ODC) I get annoying security warning messages. The
assumption here is that the ADO 2.8 security settings are NOT configurable by
developers. It appears the a solution is to explore signing forms or “fully
trusting†forms—or using a web service (preferably with ADO.NET datasets—an
implied recommendation based on a <a
href="http://msevents.microsoft.com/cui/W...lture=en-us&EventID=1032259551&CountryCode=US">recent
InfoPath webcast</a>). I even saw posts in the <a
href="http://msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.infopath">InfoPath
MSDN discussion group</a> about this matter but only sketches about setting
Internet Explorer security levels were suggested by someone <em>not</em> from
Microsoft.
</p>
<p align=left>Please see the images attached to the <a
href="http://spaces.msn.com/members/rasx/Blog/cns!1ptAuj6tD_zAu_dIRM-HCKaA!134.entry">Blog
entry version</a> of this post to view the error messages. I clearly
irritated <a
href="http://www.franklins.net/fnetdotnetrocks/dotnetrocks.aspx?showid=95">Bernard
Wong</a> at a 2004 MSDN event in Burbank when I showed him these error
messages. I just lifted up my laptop and mumbled something and showed him the
error message on my screen. He immediately said, “I’m not a mind reader!†and
did not answer the question. I did not need him to read my mind. I just
needed an expert to recognize that these error messages came from someone
somewhere at Microsoft. We need to explore the possibility that these
messages pop up for a reason and not the possibilities surrounding my nascent
clairvoyance. </p> <p align=left>I cannot be the only person on the entire
planet that saw these error messages. There must be at least one other person
who knows about these messages: the original author of the messages. Let us
begin a global search for this person (or persons) before we look for
extra-terrestrial life. I just thought I’d start with the InfoPath team. </p>