-
Can you just zip up your template and code files and attach them to a post? Under the Options tab you can attach a file.
-
You are using VSTA, right? That ships with IP 2007? So no, using Visual Studio instead won't make a difference.
You need to add a reference to your InfoPathAttachmentEncoding class. This link has some directions for how to do that.
As to your last two errors -- I searched the page with the code sample for 'string.EndsWith(string)' ...
-
Currently this is not possible. It would be a great feature to consider for future releases, however!
-
Hi -- how are you populating the other fields? Rules? If you are using rules, are they set on a field that is in the repeating group? What version of InfoPath are you using? 2003 or 2007? If I recall correctly, IP 2003 didn't automatically insert current() when you create rules, and you have to add that yourself to get the correct ...
-
Well, looking at that tutorial, you'd need to:
Add your new field to the CustomListCAML.xml file
Modify the code where it loops through the repeating table and adds items to the CAML Batch XML
Or you could just try qRules. There is a free trial available, and here's a video showing you the steps. To top it all off, with qRules you ...
-
Hi -- This sample code is for the IP 2003 Object model. You can change your form to use the 2003 OM (under Tools / Form Options / Programming) and you may find you have less errors to work through.
-
Do you know, I vaguely recall reading about that deprecation -- thank you for bringing it up and posting it!
-
Are you sure you are getting a value in NumberGroup1 and NumberGroup2? I'd check that first, if you haven't already.
-
Hi -- are you talking about using the a form field in your form as part of the SQL query in your data connection? If so, I'm afraid your choices are code or web services (we sell a great one that does this, and you can get a free trial here).
-
Are you using SQL 2005? Have you thought about using stored procedures and endpoints for this? Here is a blog post on that approach. Otherwise, I'd suggest you write your dataset into an XML node -- I'm not sure what causes that Choice section, but I'd expect InfoPath to understand XML better than a dataset. Here is an article, with ...