InfoPath Dev

Publish your form to a specific location (like C:\IpForms). Then the receiving parties should place their copy of the form into this same path location. From there they should be able to open it. Outside that, they can right-click the XSN and choose design. Then publish it locally to whereever they want, and then open it.

Hey Ty The form template is what controls the way the data is displayed. It is required to create a new form and render an existing xml document based on that Template. You must publish your form to put it into production. This is nice so when you make a change it goes into effect immediately the next time it is accessed. You can publish to ...

It could be your XPath. You are using "//" which says to return all descendant D:UT_Proposal_Material nodes. This might be picking up nodes that you weren't expecting. Try giving a more direct XPath that includes all the ancestor nodes to this one. The other trick is to create a new temporary table in your view to see what is really ...

Manual edits to the XSL is a bad idea. InfoPath provides a means of writing your own XSL (if absolutely necessary) using a Preserve Code Block -- but even though IP is not supposed to touch your code in the PCB, it still sometimes does. There's another way to make a manually generated XSL into a view (editing from within InfoPath is not ...

InfoPath only works in Browser mode from within SharePoint. You cannot run it outside of SharePoint. If you want the users to not have to navigate to it via SharePoint, then just copy the link genereated from SharePoint when createing a new browser form, and then paste that into some other web page.

The check box is bound to a field in the DOM. Just use an XPath that points to that field to which the check box is bound. /Root/Table/Row/CheckBox If you want a specific one: /Root/Table/Row[Number]/CheckBox

InfoPath gets this setting from Internet Explorer. Try changing the setting there.

I have a form that was developed with IP 2003 on the harddrive my local PC.  The form will be used by my fielders the submit information from around the world. The problem:  The Sharepoint upload works great.  However when I email a completed form as an attachment to multiple email accounts, the receiving ...

The account DBXL runs under, default is the local Network Service, would need write permissions. You might want to export them locally and then move them.

I'm having trouble calling ExportDocuments from the DBXL Administration Tool interface. I setup a shared folder and specified the folder path as: \\mycomputer\sharedfolder However, when I push the "Export" button I get the following message: "An unhandled exception occurred while calling the ExportDocuments method. I9999: An ...