InfoPath Dev

Yes the publishing is the key. That is how the location of the template is set in the resulting forms.

Either hide the submit button after the first submit. Or turn on the form library so that it does not allow orver-write of files.

Hi Clay, Thank you for your reply. Actually I already published the form both to email and network drive.  I sent the form to our SA for checking (cause I was also thinking that the problem was the access rights), however the problem is the same.  But I sent the form while previewing it, not from the Published ...

This is typically due to having a lot of data in the DB. How many records are there? For your dropdowns you would want to limit your secondary connection, often to just the one column, so you may need a secondary for each.Or create a filtered or sorted view that has a smaller subset of choices if that is applicable. I would think that ...

This is pretty straightforward. For your standard submit move the formula out of the connection. Create a field oin your form which uses the formula and therefore has the form name. Then use this as the file name source in your data connection. That way if it is a copy situation. Have a rule which modifies the filename field and when it ...

InfoPath templates are an integral part of each xml document created. They provide the information on how to display the data and how the user will interact with it. In each XML document is a link to the template it was created from. Each time a document is opened it must access the template. That is why templates are published to network ...

I think you can also use a formula to get what you need: substring-before(substring-after(/processing-instruction()[local-name(.) = "mso-infoPathSolution"], 'href="'), '"') gets me the location of my published form, regardless of where it is published.

We are getting ready to upgrade to SharePoint 2007 and shortly thereafter to Office 2007. We already have an investment in InfoPath and have on-site technical knowledge. It would seem that Forms Server just allows you to deploy forms without the recipient needing to have InfoPath. Since every one of our users has Infopath, is there any benefit ...

I know there is a path variable which can be harveted via code. It should be in a blog or post om this site.

 Is there any way to stop this error/warning message?  Per Microsoft - http://office.microsoft.com/en-gb/infopath/HA100522701033.aspx   Automatically upgrade existing forms is on.   However, every time I make a change to the template, both myself and the users receive the "FORM TEMPLATE CONFLICT  The form ...