InfoPath Dev

I think the problem is solved. Changing browser settings company-wide to less restrictive data access is evidently not necessary in our scenario. It turns out that simply adding the hosting server to trusted sites does the trick. Since the hosting server will be our own public Internet site, this does not constitute a security exposure in the ...

Ok, changing the browser settings eliminated one warning, but when trying to use NT authentication rather than SQL authentication when connecting to the SQL Server database, I get the ADO warning: This website is using your identity to access a data source. If you trust this website, click OK to continue, otherwise click Cancel. Not only is ...

Thanks, SamDahl. I'll look into the scripting angle. Referencing your earlier post where you mention changing security settings, are you referring to browser settings or sharepoint settings? (At this time, we are NOT using sharepoint services.) I've tried changing browser settings with no apparent effect while trying to run my form from my ...

Thanks, Ted. That helps, but -- if I understand correctly -- the only way to have others use fully trusted forms is for the forms to be installed individually for each user, preferably via an MSI package. The implication is that if it is a requirement that I make these forms accessible from a intranet web link, I'm stuck with the warning ...

As an InfoPath newbie, I've worked through several tutorials & exercises to work with data via main and secondary data sources. Regardless of whether I'm using a local MS Access database or an ODBC connection to a SQL Server database on our network, I get the following message when using the form in Fill In mode: ADO Security Warning This ...