-
For some reason when I attempt to access a field that exists within my Secondary data source, I'm receiving back ''nothing''. The field is currently displaying on the form, but maybe I'm not using the right field name to access it. To get the field name I: drag the control onto the form, go into Data Validation, and select OnAfterChange and this ...
-
Thanks...but you missed the first part of my question.
Note: did this question ever get answered. Can InfoPath exist without .Net?
-
-
I'm a bit confused by your ''SOLUTION'' above... Maybe its a terminology issue.
First, a ''form template'' is what you design, and a ''form'' is what
you fill out.
Second, form templates are ''published'', and forms are ''saved''.
When you publish a form template to SharePoint, yes it appears in the Library. You can republish your form ...
-
You can only use the form if you have the form template. So when you mail the form to someone from within InfoPath, you are only mailing the .xml form (not the form template). The other person has to already have the form template installed... AND they need to have it installed in the SAME location that you did.
Specifying the attachment name as ...
-
It is highly unlikely you will ever find a translater from .NET to script. Too many features would be unsupported and your code would be severely crippled.
Greg Collins [InfoPath MVP]
-
Thanx for the compliment!
I ran a quick test to rebind the main DOM to the database to see if InfoPath would add the queryView property back in -- it didn't.
It is my (unverified) assumption that InfoPath ONLY places this property when the form is first created. If you discover otherwise in your work, please let us know!
Greg Collins [InfoPath ...
-
Does the user have to have the .Net Framework on their PC to display an InfoPath form?
If the developer uses VB.Net (Duh!!!) I take it that they do, but what about script? If script will work, is there a translator out there that will change my VB.Net code to script? Although, I much more prefer the VB.Net.
-
The solution that I had was a work around, and not a resolution to the problem. The problem that exists, is that you CANNOT publish an InfoPath FORM to Sharepoint. Please comment...
Of course, after you've published your document library, you could copy the template file locally and upload it in sharepoint.
-
I'm attempting to submit and email an InfoPath form to someone else (myself actually for testing). First off, the
oEMail.AttachmentFileName = ''IPHardwareSoftwareRequest.xsn''
which is the name of my InfoPath form, not sure of the extension, (although I think I'm right)
It allows me to view the attachment before I email it, and I see the XML ...