InfoPath Dev

Sorry dude, but we can't see your code snippet.

We have a PI Edit Tool that will let you automatically move forms from one server to another. It fixes up the Processing Instruction in the form that tells it where the template is. Of course, the template must also be archived and that's the address you'll want to use. I've sent e-mail to others on our team to reply with the link.

Of course you also have to setup the workflow correctly and approve it. Don't forget that. It should trigger forward automatically for newly submitted forms. The data field idea above is for more complex triggering (for example rejection). Of course, users can use the SharePoint form library too to change workflow state.

Add a field in your form and set that field when you submit. Have the workflow trigger based on that field.

We don't use this because it's an ActiveX control and has some deployment complexity. Our Active Directory Web Service (server install) allows you to easily get AD info (including email). Check it out: http://www.qdabra.com/en/products/ADWebService.aspx

Hi Ram, This is a good idea. Have you searched on "passing parameters or passing arguments"? Lots of stuff exists in this forum that explains how to do it. Greg has at least one blog post and so does Jim, although they are quite different. The InfoPath blog by Microsoft also has a post. The other way to do it is by writing code inline ...

Quick reply for now: I believe the InfoPath 2003 SDK contains an example of Word Print Views. Have you looked at it? It will require binding the XSD to the Word Smart Doc and creating an XSL to handle the incoming XML for the print. Limitations exist and it's a lot of work, but *you can* do it. More later,

Hi Ian, I seem to recall replying to you before about Print views telling you they were hard and not for the faint-of-heart. We *have* done them several times, but we generally prefer not to because they are complicated and the Word template must be updated whenever the form changes (plus it must be installed on the machine that will print, being ...

If there's only one person using Access, you could just have an Open rule that looks up the last ID in your Access DB and increments it. However, if you have more than one user, you can't do it sequentially on the client because multiple people could open or submit at the same time and that would create duplicate IDs. The only client ...