InfoPath Dev

Ok, I'm a local admin on the WFE, so I was able to modify the zone settings.  It worked perfectly with the site in Local Intranet. This will be a definite issue not only here but with other clients.  Has there been any thought or work put into figuring out how to still get it to work in the Trusted zone for those who will have no ...

Bah!  Those settings are controlled and restricted via Group Policy.  I will go onto the server to see if I can work around it, but that would only be a temporary bandaid, because the group policy would get in the way for future production use...

This is a common filter bug. This forum has several threads that discuss how to do it. Greg Collins has a blog on it too. You have to be careful and use the preceding-sibling. Check out Greg's blog: http://www.infopathdev.com/blogs/greg/archive/2005/06/13/Using-XPath_2700_s-_2700_preceding_2D00_sibling_2700_-Axis-Correctly.aspx Regarding ...

Hi Thomas, Great scenario. Should be totally doable with InfoPath and SQL. SharePoint has some perf limits with several thousand forms but if you use SharePoint Data View Web Part on SQL you can filter to only show the data you need and get around the limitations. We have several solutions in the 100k+ range of forms and visibility is fine with ...

Another alternative is to write code. It won't be as secure as using a Web Service (SharePoint's or Qdabra's) but you can do it. Search the forum for LDAP. There are many examples:  http://www.google.com/cse?cx=003654972516704994317%3A4j0mji2l1rq&ie=UTF-8&q=LDAP

Trusted Sites run at lower permission than is necessary for .NET code. QRules is a set of .NET assembly that provide common functionality. As such, it needs to run as local intranet or just default (nothing) but not Trusted Sites. Trusted Sites actually lowers the permissions and prevents .NET code from running in an InfoPath form with Domain ...

1) Started by previewing but then saw the requirement for it to be published and still got the error.  2) It is a Trusted Site, so I will change and check. 3) The URL is a copy and paste from the address bar when browsed to the doc lib 4) Blank template was created without checking the box for browser-enabling, and the form is in rich ...

Hi Clayton, Thank you for trying qRules. Are you trying to Preview the form or publish and run? Is the site you are publishing to in Trusted Sites? If so, remove and add to Local Intranet. If that doesn't fix it, it's possible that the URL is wrong or that you are trying to use it with browser forms (not supported). Once again, THANK ...

Why would there be a policy not to use SharePoint's built-in ability to expose user profile data to developers?  InfoPath can consume and display all profile data for users without a line of code, so that is a very strange policy. Your alternative is to use the Qdabra Active Directory Web Service, which will tie straight to AD instead of ...

Thomas, you know how I feel about this, but I'll wait to see what the Qdabra folks think.