InfoPath Dev

Thanks for your kind words!

Ah yes, my mistake. I forgot that rule actions don't let you modify the field xpath. Unfortunately, it is set up so that if you try to edit them manually, it causes further problems. What happens with rules where you set a value in a repeating list is that the value of each mathing field in every row gets updated. This is sometimes helpful, but ...

Glad you got that part figured out. Code is not affected by designer changes--you have to keep that up-to-date manually. Try removing the onload code (or as much as possible) and see what difference that makes. Perhaps there is something very inefficient happening. Also, if you have any OnAfterChange events, make sure that those aren't getting ...

You might need to do some work to get some cleanup to happen the, like haveing a rule one the field which sets the field with a substring of itself... or perhaps have your comparison just compare the strings before any ''T'' character (if it exists). Not sure why the web site is serving up the old form...

Try placing an expression box or a plain text version of each date where you can see them. Perhaps what is happing is has nothing to do with the date, but the time portion of the date... For example you might find that you are trying to compare: 2007-03-12 against 2007-03-12T00:00:00 or something like that.

Normally no. What is the error, have you checked around in your code to see if there was something specific to that view?

With what you want to do, rules should cascade, like dominos falling. Using following-sibling::my:RowNode[1]/my:FieldName to set the row field should work. Note the [1] filter is essential in the XPath to state that you want the very next sibling. Then the rule on that next row should do the same to the one following it, etc.

Normally I would tell you it is because you are using a secondary data source... but in your case it is the main data source. Now, I have not tested this, but it could be because your main data source is ''really'' a secondary data source (i.e. a Web service)... You should be able to tell whether this is the case by designing 2 new blank ...

Sorry, this is not possible. And unfortunately, InfoPath cuts off the list items at the length of the drop-down box. It would be nice if it would extend the list beyond the box width to the width of the content... perhaps in a later verison!

Matthias, I am glad to have been able to help you. Working across forms can be very frustrating if you've never done it before -- and even when you have done it before. I'm sorry it took us so long to get it working for you, but I'm glad that you have it working now! Keep up the good work--it gets easier the more you work with it!