InfoPath Dev

Thanks for the response. I don't think it's a case sensitivity issue. I should of mentioned before but it seems to be error seems to be comming from the two lines below XDocument.UI.SetSaveAsDialogLocation("C:\") XDocument.UI.SetSaveAsDialogFileName("form1")

We successfully work around it by not hotlinking to the form,. We make the users open the form lbrary and click NEW to create the form. When we do this, we never get the error.      

I suggest checking the capitalization on isCancelled, performsaveoperatoin, and returnstatus.  I reckon those are case sensitive.

It looks like this topic was started about 3 years ago...  Has anyone ever been able to fix or work around this problem?

How can I display a value selected from a drop-down list without it being underlined on the form?  Is there a way to do this without creating a separate print view?  I'm using InfoPath 2010.   Thanks!

Hi, Is there a way to print multiple views one after the other? If I just change view and try to print, it doesn't work. I guess I'd have to catch some ViewLoaded event? Does anyone know what that event should be? Or maybe there is another way to do it? Thanks, Michael

Thanks for the information and after a few mis-tries, I've got it working brilliantly!  The Carriage return in the XML file is a neat trick to be able to separate the sections as the concat won't allow for separation of field results nor the formatting to look reasonable. Thanks very much for your help over this one.  Alan ...

Morning all! I am trying to create an OnSaveRequest event that sets the SaveAs default location. This is what I have so far. Sub XDocument_OnSaveRequest(eventObj)      If evenObj.IsSaveAs = True ...

Hi, Help, please. First of all, I am running SharePoint 2007 SP2 Enterprise in Spanish and MS InfoPath 2010 in English. I have a browser form with a submit button and I want to put a second button to save only the changes. After the form is submitted the first time I want to be able to save the changes without overriding the ...

For the fields that are not repeating like subtotal, tax, etc. you will need to move that outside of the repeating table.  In terms of your data source, you'll have to create fields outside of the repeating node and have those fields be displayed under the repeating table to achieve the same look and feel that you have in your ...