InfoPath Dev

InfoPath and SharePoints are totally new to me...Can anyone help me decifer this error?

"InfoPath cannot open the fallowing file: http://All....Task.xml?Source=http://all....Task.xml. The Form Contains schema errors. and then I click More Details and it tells me:

"Element '{http://schemas.microsoft.com/office/infopath/2003/myXSD/2008-03-28T21:09:50}LumbarRange' is unexpected according to content model of parent element '{http://schemas.microsoft.com/office/infopath/2003/myXSD/2008-03-28T21:09:50}myFields'."

Please Help and Thank you for your time.

Hi - did your template recently change?

If the template was changed, and not set to update existing XML, you may get schema errors. BUT, if you changed your template schema in a way that may cause existing XML to suffer data loss, you'd want to be careful about using this setting.

So, I'd say the first question is - did you or someone else change the template that is used to open this XML?

Yes it has been changed, I was given the job back in June to update it and the whole process has been a mess ever since due to not having training in doing so. Is this "update exsisting XML's" option just a button I check during the publishing process or if it is something that if it was never done prior it is too late?

It is in the form options - If InfoPath 2007, under Tools > Form Options. If IP 2010, under the File Tab - Info - Form Options. Then select Versioning.

I do want to warn you however - what changes did you make to the form's data source? Did you just add new nodes? You didn't delete or move nodes?

Because if you deleted or moved nodes, if you update your existing XML when you open them with your updated template, those nodes will be deleted - along with their data.

You can preview your updated template with an existing XML to see what the effect will be. Save an XML locally from your SharePoint library, then in the same Form Options dialog, select the Preview section. The center portion allows you to browse for an XML to preview with. Then you can see what happens with existing XML and your new form in relative safety.

Versioning is currently set to: "automatically update exsisting forms" does this mean that the schema error could be caused by something else?

Yup, could be. I've occasionally seen a template set the max version to upgrade incorrectly (this is in the manifest) - you could try setting it to NOT upgrade, save, set to upgrade again and see what happens - save a copy first for backup. And then preview it with the XML that is failing - that can be your test so you know whether the template will work before trying to publish again.

Oh, and you don't have any custom code in this form, do you?

I will give that a try this afternoon and if I have no avail then I will be back, I do not beleive I have any custom code, I did mess with some coding in the updating of the form (which actually could be causing this problem anyway) Is there a way to check to see if someone prior had custom coding or is it one of those things that I would know I have it if I really did?

In the Form Options dialog, check the Programming option. You can see where the form thinks its code files (if any) are located there - as well as remove code.

The only thing that I can click in the programming dialog box is "Remove Code" and I assumming I wouldnt want to do so. Thanks again!

I am now confused, I just did the versioning thing you told me to try and locally all of my xml's open with this form (108 of them) I publish it to the server and I am back to getting the same error about the schema.. Any other suggestions?

Oh, wow - that's interesting. This is a browser form and you have the issue when opening in the browser?

Now, What if I told you I can get them all to work just fine on other computers..

Through the server that is, the exact same way that gets me an error works just fine on other computers..

Even if you have Automatic Versioning turned on, I believe that InfoPath will refuse to open a document if it contains nodes that it is not expecting in the main data source.  This will happen if you have deleted or moved any nodes in the data source.  Did you delete or move the LumbarRange node in the main data source?