InfoPath Dev

Afternoon (or it is to me).

I am having an issue with all infopath forms for a particular machine in my organisation and was wondering if anybody could give me some advise as to what may be happening.

What seems to happen is when a user opens a form from a works order system developed internally on SharePoint, none of the fields can be edited, it more or less displays the form as a picture in infopath.

However when this same form is opened on a different machine, it works as exactly as expected and the form fields can be edited.

 

Any suggestions as to what may be happening would be appreciated

Thanks

John

Hi John,

That's strange. Is he trying to open the form in SharePoint? I don't have a clue, but it might be worth it to check if the user has the correct permissions in SharePoint. At least contribute access with read/write permisions.

 Hi Jo-Anne

To clarify, the infopath template is held in SharePoint and the XML document will save to the SharePoint form library, but because of some content in the form not being available in forms services, the form is opened by the local infopath client to enter the data then saved back to the SharePoint form library.

Thanks in advance for taking time to answer :)

 John

Hi John,

Do you have some sort of permissions/rules running in your form - for example, if current user is not the one who created the form, it switches to a read-only view?

Hi Jo-Anne, I work with John and this is a form that I created. There are a couple of checkboxes that can only be checked if the user is the same as that selected in a drop down list, but other than that there are no form restrictions. The form is being successfully used by over twenty other people. The main thing to point out is that the form isn't displayed as read-only in the normal sense of the word, i.e. you can still highlight/copy text or click on hyperlinks in a read-only form, but this looks and acts more like a jpeg image off the form. The things we've ruled out so far: the same form is used successfully by many people, the user that this affects has got identical site and AD permissions as everyone else. John created a new form with just two text boxes and exactly the same problem occurred with that. I believe the user has had Office 2007 completely re-installed. One thing that may help is that when the user opens the form it initially looks as if it's going to open in IE (even though this is not enabled on the form) before it actually opens. My thoughts are that there's something wrong with the way Windows is trying to open the form rather anything wrong with the form itself. Cheers, Phil

It sounds like a machine issue, doesn't it.

What happens if another user signs into this user's machine? What happens if this user tries a different machine?

What are the file associations for XML files on this machine - If you save one of the XML locally and right click it and select properties, what is it set to open with? What about an XSN?

If you put the template on the user's machine, can s/he preview it?

Sorted! Just in case anyone else comes across this issue, apparently it is a file association issue caused by the Office 2003 compatibility pack for Office 2007 not being uninstalled after upgrading to Office 2007. I'm told the details are on TechNet somewhere but we fixed our issue by re-imaging the user's PC.

Thank you so much for taking the time to post your resolution to the issue and what you learned! I'm sure this is going to help someone else - and I'm glad you got it figured out. :-)