InfoPath Dev

Hi Rob, No, InfoPath doesn't support this.  For small field validation (16 characters or less), you could break them up into 1 character fields with each one next to another so it looks like a composite field. Then, you can right click each field and on the Display tab check the "Limit text box to: 1 character" box and ...

Hi Rob, Yes, this is certainly a valid flow scenario for forms that submit to DBXL where SharePoint workflow is also involved. I'm assuming that you have turned on property demotion for your fields so that you can edit them in SharePoint. This feature is turned off by default and it is not a best practice because SharePoint doesn't ...

Yes, but you can just add concats if you need more - e.g. concat(concat(field1, field2, field3, field4), field5, field6, ...)

That's great. You could add a condition on the workflow that is based on a promoted property from your form. That way you can control when the workflow actually does stuff.

Hi Selmore, I'm not sure if you are using a list form or not, but neither list forms nor library forms support repeating items. Here's what you should do.Create a full fledged InfoPath form template from scratch (not a list form)Add a repeating group to your form and add a non-repeating Person field underneath it.Add a data connection ...

Create an InfoPath form that you use as your web page. The form can dynamically create the URL using XPath's concat function. Of course, you're just using InfoPath as a Web page design tool. It won't submit anything. InfoPath Web Part can be added to the page where you want it to appear.

Hi Marzipan, Yes, you can use ADUserInfo.asmx methods from ASP.NET. Jimmy posted a sample showing how to use DBXL from ASP.NET. Same sample should assist you. Just replace the relevant calls with the ADUserInfo.asmx you are interested in. Here's the link: ...

Hi DaveC and welcome, Shiraz Cupala blogged a technique showing how to do this several years back. http://www.infopathdev.com/blogs/shiraz/archive/2007/08/16/best-way-to-launch-forms-from-web-pages.aspx Good luck!

Hi MHoel and welcome, You don't need code for this. Just add a print view and associate it to the view that you want to use it when the user clicks ctrl-P, Print. It's in the Page View tab on the ribbon. Click on properties for the view and the Print tab should allow you to associate a separate view to print. Good luck!

Hi TiltnSpill, The only way that this could be related to 64-bit InfoPath client would be if the output XML were different. Take a look at the XML forms generated in Notepad and see if you can figure out what the diference is. My hunch is that the 64-bit change is a red herring. Why? Well, there's no connection from the client to the ...