InfoPath Dev

Yes, I built the form so I am sure there is no conditional display, enablement, or read-only logic.

We just have multiple forms in the form library.  They are all based on the same form template and when you submit the form to the library a new .xml file is created. On some forms, users are unable to edit previously populated information in fields like a drop down, text input, or date picker when the open the form from the form ...

We have a SharePoint form library that contains instances of the same form template (e.g. each form submission saves to the form library), but it seems that some forms are having an error/issue that prevents us from editing the data in the fields.  This was not part of the form design, but seems to be occuring in multiple forms but not in ...

  Is there a way to replace the InfoPath 2003 template in a Visual Studio project but keep all the code behind?   I have the following problem:    My desktop was lost by movers in a company move and the most recent version of the VS Project of an application I was working on was not in source control and was on my ...

We have a SharePoint form library that was built using InfoPath 2003 and SharePoint 2003 and uses form fields/library columns to filter data with for information hiding/ease of access (using Greg Collins' ...

We have a problem where the majority of our users are on InfoPath 2003, but some are using InfoPath 2007.  We use a field called "Title" as the filename/key and it often contains commas and becomes something like "Smith, Joe - Employement Information.xml".  However if a InfoPath 2007 user open an existing form like ...

We have an InfoPath 2003 form that submits/saves to the SharePoint Form Library, however when the form is re-opened one of the key fields is not editable any more.  I have looked through as many fields as I can to see if there is a rule that is tied to an odd field that locks the key field/makes it read only (it does not appear to truly be ...