-
My suggestion to check with an Access newsgroup/forum was not to suggest that it was a problem with that application, just that someone with a core understanding of that application (with some InfoPath background) might have more insight as to the cause/source of the issue.
Anyone else with ideas -- feel free to jump in at this point.
Good luck!
-
Can anyone else help out Eleanore here?
-
I'm glad to hear you figured it out and got it working! Thanks for letting us know!
-
The failure is coming from: root.SelectSingleNode("my:myFields/my:eName", NamespaceManager).Value.ToString()
The failure is that the node is invalid. Are you sure that it is "eName" and not just "Name"?
Otherwise, I suggest looking at an XML dump of the form causing the issue to see if the field is actually ...
-
Hi Thanks for sharing... Make sure the one line should read:
BACKGROUND-REPEAT: NO-REPEAT;
You may also find that you need to remove the shading from the button, which can be done in the designer. For an XP-style button either the border or shading must be removed before you'll see the image.
Please refer here for ...
-
Great! Glad to have helped out.
-
What do you mean by "when I set these 2 data sources" ?
-
I see Clay responded to your newsgroup posting of this same issue. See if that is of any help.
-
Its probably a runtime issue.
Try building out a new blank form as minimally as possible to do the same submit and see if it persists in the new form. If not, there's something else wrong in your current form. If it does, maybe contact an Access newsgroup/forum to see if anyone there has an idea.
-
If you have an XSN, rename it to have the .CAB extension instead of .XSN extension, and then extract all the files into a folder.
Once you have all the files extracted, you can manually change the XPath using notepad.
If THIS was the reason you could not open in InfoPath, then you should be able to now. To do so, right-click the manifest.xsf ...