InfoPath Dev

The XML is not the issue.  This form works fine for everyone else, it is only one person who is unable to view it in InfoPath.  It is instead showing up in her browser as XML.  I would assume that there is a setting on her machine that needs to be changed so that it uses InfoPath and not the browser, but I don't know what ...

Sorry for the confusion.  You are correct - when I said "regular" InfoPath forms, I meant forms that we have published to a network drive and have a link to within a Sharepoint document library.  Those open properly for her within the InfoPath application. The issue is with the forms published to a Sharepoint form ...

Yes, she is able to open all other docs.  It's literally just the forms that are published from InfoPath to Sharepoint form libraries that are causing the problem.

I had originally done a quick look at the IE settings but I didn't see anything that seemed like it would affect it, although maybe I missed something.  I did try it in Chrome with the same results though so I don't think it's specific to IE.

Thanks for the reply, Hilary.  I checked my associations and hers and they're identical so I don't think it's that.  And as I mentioned, "regular" InfoPath forms open properly for her in InfoPath.  It's only the ones that are published to a Sharepoint library that are causing an issue.

I have an odd issue.  I have one user who is no longer able to open the InfoPath 2010 forms that we have stored in Sharepoint libraries (we use WSS3).  She was able to access them properly a couple weeks ago but now they don't open in InfoPath, they open in her browser as the HTML code.  No one else is having this issue and ...

Jimmy, thank you, thank you, thank you!!!  My form is working properly now.  I really appreciate your help with this. 

I put the following into the filter as an expression ../@PID = current()/../intPropID but it's still telling that it's not a valid location.  I also just tried typing it into the XPath as ,,, and ../@PID = current()/../intPropID] but it gave the same message.  "../intPropID" does not point to a valid location path ...

Thanks for the suggestion, Jimmy.  Unfortunately, it's still not working.  I created the ReProcess field inside my repeating section.  I have a rule on open to change ReProcess to 0 and then to 1.  I copied the rules that are on change of Property ID over to the ReProcess field.  However, the rule is identical on ...

One additional note:  if I disable the rule to update the collateral fields on open, then the information is correct when I reopen the form.  However if any changes have been made in our systems to the fields we're pulling into the form, the user will have to change the Property ID and retype it in order to get the ...