InfoPath Dev

If you promote a field in the library form, then you can connect another InfoPath form to this library using a secondary data connection and populate a dropdown based on this field.  Not sure if this is what you are asking.  If not, feel free to elaborate on your scenario some more I can try to help!

Its not straight forward to actually change a control in InfoPath.  What I would recommend is to insert both a list box and multiple select list box and then use rules to hide one of them based on the selection of Choice Zone.  Each of the controls requires to be bound to two different type of fields, so make sure that when you submit ...

Check out this tutorial video I created that describes how to create cascading dropdowns in InfoPath: http://www.youtube.com/watch?v=SH7xUEcQwwg If you have any specific questions, feel free to let me know and I can try to help!

People picker is one of those fields that is tricky to promote.  You could just use a text field instead, but will lose the communicator widget in the browser.  Also when you set the userName() be sure to set the AccountID field.

Consider checking out qRules which containts an Insert function that does exactly what you need.  A trial version can be found here: http://www.qdabra.com/en/products/qRules_new.aspx

Make sure you are setting the AccountID field in the people picker field.  I would also recommend setting the field via form load rules instead of default value.  Hope this helps!

qRules has a DateDiff command which you can use to easily determine the difference between two date fields: http://www.qdabra.com/en/products/qRules_new.aspx Otherwise, you're likely looking at some custom code to implement this.

Do you want to hide an individual row that doesn't match or do you want to hide the entire repeating control?  If its the former, you could try using a formatting rule.  I think you also may want to select just the CTIssue field instead of ALL.  If its the latter, then you'll need to surround the repeating control in a ...

It looks like the addSeconds function adds the seconds correctly but is removing the time zone stamp from the date which is why you get the addition of 5 hours. Did a quick search and couldn't find a reason why it does this or a good workaround.  But if you know you're always going to be in the -5GMT zone, you could simply add a ...

What are you entering as your second field?  It has to be in seconds format so likely an integer.  You cannot put something else like a time field.