InfoPath Dev

It sounds like you are using the default value behavior of InfoPath. You would be better off writing code to do this because you have greater control over when and how the update occurs. Greg Collins [InfoPath MVP] InfoPathDev

You can use code to do your conditional formatting testing by calling xdExtension:MyConditionFuction(). Return a boolean value. Greg Collins [InfoPath MVP] InfoPathDev

My guess is that the user has modified their Windows settings to engage Large Fonts or some other Windows accessibility feature. Greg Collins [InfoPath MVP] InfoPathDev

Try using Type.Missing for the other paramter(s) Greg Collins [InfoPath MVP] InfoPathDev

That should be possible. You would just have to transfer the data from one DOM to the other and then submit. Greg Collins [InfoPath MVP] InfoPathDev

If the field is formatted as a number, the leading zero gets dropped. If it has formatted turned off (None), the leading zeros will remain. Greg Collins [InfoPath MVP] InfoPathDev

This sounds like it could be a timing issue. That perhaps the printer change is not actually happening until after the first printout occurs. Greg Collins [InfoPath MVP] InfoPathDev

I believe that you cannot have a filter ([]) directly after a self (.) or parent (..) reference. You might try updating the XPath to something like the following: <xsl:if test=''not(../..node()[@my:UniqueID=$val] or $val='')''> Greg Collins [InfoPath MVP] InfoPathDev

The context for the button is the row of the table... meaning, if you have a data source that looks like this: Group1 Group2 field1 And a repeating table that looks like this [button][text box] [button][text box] [button][text box] Clicking on the button will put our starting point for selection in Group2. It sounds like you already had ...