In one of my customer's MOSS implementations we're using SharePoint's resident permission management to control who has access to what InfoPath forms. The issue we came across is that if a user has read-only access to a form and opens it, they can see the Update button. Clicking it does error and denies the change, and after the error the user gets the typical form closed message. We wanted to hide the button from the view of a user who has read-only permissions to deny the error all together... [More]

If you haven't experienced it already, when you have an InfoPath form live on your server, and you make a change to the schema of the form and upload it over the existing copy, your old forms won't open. There is a work around we have applied with our customer which works well for us and I'll continue to explain it here.  If you are stuck right now, and you already uploaded a new form and lost access to your old forms: find the previous version. Whether from backup or source safe, roll back... [More]

A while back I ran into this issue: I had two web parts in the same project but I wanted them to share settings. As my experience as an ASP.Net developer was pointing me to use the web.config file, instead I thought SharePoint must have something similar to this without me having to mess with the web.config file. After searching and posting on MSDN, I did finally find a solution that uses the properties of SharePoint Sites and Webs. Below is a sample code that stores the Employee Prof... [More]

One great feature of SharePoint and versioning is the ability to have versioned comments. This can allow a small discussion to occur on almost any item. It also allows someone to keep a running log of notes on certain items. I had the wonderful task of figuring out how to get this to work the same in InfoPath. Below is a function that will append the notes into a repeating group. On submit of the form, I call this function and it works great, everytime! public void AddAnalystNotes(){ try&... [More]