InfoPath Dev

I published a form in a Shared folder. When I tried to access the form it give me an error that the form don't have access to the resources of the computer because it's no Fully Trusted. I read about it and found out that I have to Sign my Template for the form to be fully trusted. So I went to Tools->Form Options-> Security. Checked ...

Using thisXDocument.Uri you can get filename, set this in a field and in the design mode bind that field to a Control to show the value.

Hello. I am fairly new to Infopath, so I apologize for the newbie type question. I have developed about 8 Infopath forms for our helpdesk ranging from system access request to account change-- on and on. These forms include hyperlinks to one another, they are pretty detailed/lengthy forms, but nothing off the wall. Everything is standard ...

You might try the IP2007 beta. I believe it has better data base support. But in general the one-to-many kills submit for DB in IP2003. A Web service would be required in this case.

Set a default value formula on the node you bound the drop-down to, and turn off the check box which says to update it every time the value changes. The default value would need to be set to something like: ../preceding-sibling::my:RowName[1]/my:FieldName

There is a check box that says whether the default value formula gets updated every time... you might just need to uncheck this.

You need to use the current() function... check out the following articles and example forms: http://www.infopathdev.com/search.aspx?s=current()

InfoPath uses XSLT to generate the HTML/CSS that is used to display the form. Click on the Downloads link in the site menu... there's a viewer you can get from there.

For the second list box to show the right value, please review the following articles and example forms: http://www.infopathdev.com/search.aspx?s=''Cascading%20List'' For the print issue, it sounds like what you need to do is create a separate ''print view''... you can create a new view for printing, and associate it with your editable view so ...

Yes the DOM property itself is read-only... but the actual nodes you select beneath the DOM are not read-only. Subtle difference. Glad you got it worked out!