You searched for the word(s): 12
-
Not at all but what do you mean by current main data source?
-
Because based on the error message, it appears that the XMLs that are failing to open have a LumbarRange node directly under myFields. Would you mind placing one of these problematic XML files, and a screenshot of your current main data source, in a ZIP file and attaching it to this thread?
-
The form is stored on a server so those computers wouldnt have any version of the templete.
LumbarRange for some reason is under the parent MaxLumbarHeight.. I am officially hoping that if I move that to be under MyFields that it will work, why do you ask?
-
I think the likely case is that the other computers have an older version of the template and that is why they can still open the forms. You probably have a newer version that has been modified in such a way that the documents won't open in it anymore.
That is my guess anyway.
Regarding my earlier question, when you look at ...
-
Anything is possible, What I am wondering is if because I have other versions of this same infopath form template on my computers drive if that is why I cannot open it, I have gone around to a handful of computers now and I am the only one that it doesnt work on.. Would still having saved versions have anything to cause this, what would happen if ...
-
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?
-
Through the server that is, the exact same way that gets me an error works just fine on other computers..
-
Now, What if I told you I can get them all to work just fine on other computers..
-
-
Oh, wow - that's interesting. This is a browser form and you have the issue when opening in the browser?