-
Hi,
I have a form in which you select a field value from an SQL db data connection, then click a button to launch another form and send that selected value to the new form. This value arrives in a query field in the new form that is connected to a similar data connection. The new form will query an SQL db based on this value ...
-
I've been trying to ge a solution to this for months. I've been on the Microsoft public forums, private MVP forums, and in personal contact with MS InfoPath employees... all with no solutions so far.
If anyone does have a solution to this, please let us know!
UPDATE: The solution can be found here: http://braintrove.com/article/53
-
Are you per chance trying to switch views while a switch view is in progress? For example, you click the button, it switches the view, but the code behind the button tries to switch to another view?
This will cause the issue (or something similar to the one) you are seeing.
-
Sounds like there might be a difference in the returned XML structure... the schema has likely changed between then causing the issue.
-
The problem is most likely that there is an error in a different view. For example if you have 3 views and 3 required fields in your form template, and each view contains only one of each of the required fields... then no matter which view you are on, you are only seeing 1 of the required fields. Thus if you fill it out and try to sign/submit, ...
-
So what you are looking for is a way to build a dynamic form? It is possible to have a form design such that it pulls in a secondary data source (another xml file, etc) and constructs itself based on that. A valid example of this is a survey form. There would be the form that users open to fill out the survey, and the one that the admin uses to ...
-
InfoPath does include an attachment control. The attachment is stored directly in the document as a base-64 encoded string.
-
You basically have it. The one condition is that you must use code. There is an Errors collection--check to see whether there are zero errors. Errors occur because required fields (red asterisks) are not filled in or because of invalid data (text in a date picker field). This soundsl like all you need.
There is a way to call into code from ...
-
Your first question -- yes, those assumptions are correct.
Quotes are there to separate the code from the rest of the text.
The equal sign after field1 stands for "is defined as".
The ../ means to go to the parent node.
-
Thanks for the response. I had been thinking about that solution. I was kind of hoping for something more straightforward, but I think that will work fine. Once it is set up it will be easy for the users to use.