-
Hi --
Is your drop down list populated from a secondary data source? Because, basically, you'll need to submit any 'new' items to that data source, then refresh it for them to show up in the current form.
If your form itself is bound to a DB and you submit info from it to a DB, another option that may be workable for you is to use ...
-
Thanks so much Qazi
I did that now and i was able to open the forms from the shared folder without any warning or error messages
Thanks a lot
-
Yes the GUID column in the SQLdb is the primary key. I am an old VB programmer and this has worked fine to let SQL generate the newID but Infopath will not allow me to submit the form when I have not assigned a value to field in the DB that does not allow nulls....
Thanks for your help
-
Hi --
I'm a little confused on what you are doing. The section on your Current Form screen shot is currently showing all the citiations for all the questions? And it should only show the citations for question 18? That would be a matter of filtering the repeating section... is that 'citation' repeating section nested in a section ...
-
Hi:
To use InfoPath's native submit capabilities, you need to design the form off the database, I'm afraid. Otherwise, I imagine you could write custom code for this. Our web services submit to SQL (and SQL Express is free), if that might be a useable option for you.
-
Is your GUID column your primary key in your DB? I was trying to test this, and SQL was quite upset that I wanted to set my GUID column with a calculated default to the PK.
(If you don't want to write code for a GUID, and if you are using IP 2007, you could give qRules a try. GenerateGuid is one of many cool commands.)
-
Is 'view' supposed to be capitalized in the line with the error? What about 'mht'? In the MSDN documentation, it looks like View and MHT.
-
Hi -- are the questions different depending on which department is selected? If so, you may want to use a secondary data source to provide the correct questions for each department....
-
Couldn't you submit the entire XML of the form as a string to your "WebApp" application? Then in that application, parse the data from the XML?
-
You could programatically generate the XML for the second form -- where will you be storing the form? SharePoint? The link would point to your generated XML -- be sure to include the processing instructions so that the XML opens with the correct template. When you generate the XML for the second form, you could get the info from SQL from your ...