Skip to: Site menu | Main content
In web development and programming, I often come across useful tidbits that solve a problem for me. I often have those problems again and can't remember that tidbit. Now I will. Maybe you can benefit too.
I've seen this a couple time and have found help elsewhere, but thought I should add it here too. If you're messing with the header on an InfoPath form and end up not being able to open it due to an error with a header tag in your .xsf file, it's fairly easy to fix. Kinda.
If you have worked with SharePoint, you are probably aware of the fine grained permissions that can be set anywhere from the site level down to the individual document level. You have probably run into the usual problems associated with assigning permissions, inheritance and problems with breaking inheritance. But occassionally even when the permissions are set correctly for a given user, they will still get a permission denied error when trying to access a document or form.
If you publish InfoPath forms to SharePoint, or this may even happen if you put them in other network locations, you may find that when making an update to the form, some users continue to see the old version. I recently tracked this down as being caused by InfoPath caching a version of the form on the users computer.
- DevGuru - Transact-SQL Reference - Google - More Helpful Links
.NET | AJAX | Apache | ASP.NET | Browsers | C# | CSS | IIS | InfoPath | JavaScript | MS SQL | MySQL | PHP | Search | Security | SharePoint | VB.NET
User: Pass: