InfoPath Dev

UPDATE: I ran into an issue with step 8 of Patrick's steps.  I recently realized this numbering was not working correctly in a form I created when I tried to replicate these steps in a new form. My former form numbering appeared to be working only because the default view is being sorted by ID in descending order.  ...

I have one form template in a library.  I've revised the template dramatically.  I would like to publish the 2nd revised template to the same library but I do not want the new template to override the existing forms when they are opened later.  I believe I have to publish each form as a content type to do this? Is ...

I am using log to history with each status change on an InfoPath 2007 form but one log to history is replaced by the next one so that only the most recent log to history is recorded. Is it possible to append to each so that all phases of log to history are recorded on the Workflow status page under Workflow history?

You might look into using xml expressions to accomplish that complexity in one condition, which I am no expert on. I think QRules could help you here. I would also consider looking into setting up User Roles. (I use InfoPath 2007, Tools>User Roles.  Add a role then name it anything, assign users name from Active ...

Thank you Jimmy.

So I guess I'll never know how to use this since I am either blind or it is named something different in my version.

I tried this and it worked for me.  I attached an example. Type a line press Enter.  Type another line press Enter.  The text will left-justify by default  but perhaps you can play with  positioning using &b or using the space bar... Page &p of &p  Printed on &d     

I haven't tried this but I found a post http://www.textndata.com/forums/footer-176889.html  that says you have to add  physical line breaks by pressing Enter. I had a couple minute to spare so I did a quick google.  Hope it helps you. If that doesn't work search on soemthing like: "line break in footer ...

Solution to my problem was to remove a  condition in finishedLoading rules that fired off only when a form was new. I removed the condition entirely, and now the new fields are happy.  Thank you Ernesto for pointing that out and for the tip on finishedLoading best practices!

Yes and please.  I will email it to you.