InfoPath Dev

Yes, this approach "kind of" works in theory, since I started this but decided different approach.  At the end of the day, we could get away with a save really being a Moss Library submit, the nomenclature to the end user doesn't really matter, I have all custom buttons on the form, again, completely removing the InfoPath ...

Good luck. Let us know what you find after you've diff'd the two forms.

I am at a similar issue with SRS on a project. It is the "Double Hop" problem with IIS.  Unless you use Kerberos, you cannot get the Windows Authentication to pass to the second server.  I am going to use a SQL account for the second jump. You can search on double hop to see what options there are.

Hi Clay, thanks for Response. Even if i enable the WebServiceProxy in Central Administration. - No Luck! - But difference here is that now the current user-account is mentioned in the moss log (Faild to login with domain\user). MSDN says the WebServiceProxy routes the Application-Pool-Identity to connect to the 3-rd Tier. ??? When i change the ...

You're mentioning XmlFormViewer so I am assuming you're hosting Forms Server in your own ASPX page. While I am not aware of any official blessed way of getting notified on save there is one thing you can try. The "save" button is nothing but an Anchor tag with an onclick event. Since you can run javascript in your ASPX, try to ...

Are you posting this form to a form library in MOSS for example?  If so, you don't need a line of code to get the existing name.  1) Create a new receive data connection  2) Choose the SharePoint library in question - - where it has been published and where documents/forms are being saved 3) Select the fields to bring in, for ...

Yup, ignorance exposed.  I am working with InfoPath Forms Services, managed code and InfoPath 2007 within a MOSS Environment. There is no custom action or custom "save" event allowed for Forms Services.  I believe you are mixing  up context here/don't understand what I was trying to do/fix. In fact, ...

I was finally able to resolve #2 by extracting the source files (File menu / Extra Form Files) and modifying view1.xsl in the following ways: Manually added <option>Select...</option> below the <select> tag. Removed an extra <option/> tag that was somehow introduced into the code (InfoPath 2003 bug?) that is creating ...

Hi,  I thought I correctly configured my submit option to the SharePoint site but it seems that users can't submit their form.  I can open and submit forms but they can't.  What's up with this?  Also, if I loaded the template on the form library, can I get it to appear on the SharePoint site so users can go ...