InfoPath Dev

If export to PDF is not supported in browser enabled forms, then you will need another method. There are lots of products on the market that can produce a PDF based on an HTML page or can generate one on the fly. Perhaps one of these could be incorporated into an ASPX page that generates a view of the form from the saved XML file. There might be ...

You need to use a DAVAdapter to save your created file to SharePoint. So long as you create a full InfoPath formatted XML file (get a sample XML from FORM 2), then it will open just fine in XML if it was saved out to SharePoint correctly via the DAVAdapter. You'll likely have to do a little research in how to use the DAVAdapter to accomplish ...

This is not a straightforward thing to do. Essentially the process is, on load you check the current form against the one stored in your system, and if it doesn't match, you tell them to go open it from the appropriate location, and then close down the form. However, you need to keep the forms more locked down and out of the reach of users. ...

Great! Glad to hear it's working!

Ved, your code doesn't really do much. You could set both connections to query on load, rather than on change, and you'd get the same effect without the additional wait time after each change. This is because you are not doing anything in your connection to filter your results. And since you mentioned you have more than one pair of these ...

Phil, here's an article I wrote a while back that shows how to do just this: http://www.infopathdev.com/blogs/greg/archive/2004/08/16/Make-a-Filter-Work-Automatically-With-No-User-Interaction.aspx

You use xsi:nil="true" if you don't want the user to be required to fill out the field (or in this case, attach a file). Without that attribute, the field will be required by the user (i.e. red asterisk). It's your choice really. If you add the attribute, you'll need to follow all the rules for adding an attribute with a ...

Yes, it's one place that's really lacking in InfoPath: the ability to elegantly deal with repeating structures via rules. Maybe the next major release...

I do recall seeing that in there. Either entry point will change the same system setting. Thanks for writing back on this!

Yes, all C# code is case sensitive. Hard lesson, but you'll not forget. Glad you got it working.