InfoPath Dev

It sounds like you are asking why the first row of a repeating section is being displayed by default. This is because that data is present in your XML when you start your form. You can go to Tools | Default Values and tell InfoPath you don't want a default row inserted.

Need to place a Section around that row (i.e. need to break up your layout table). Then add the conditional formatting on the Section.

concat() is not directly supported in list boxes. However, you can manually modify your XSL to include a concat() function to make the drop-down list box display the two fields as one. I believe this has been discussed a couple times before in these forums.

Text is stored in the XML in ASCII characters. There's no encoding specified. English characters are all going to have ASCII values between of 32-127. Anything above that would be either a special character or a foreign language character. A quick internet search revealed that Hebrew fonts map to ASCII 224-250. The other issue you run into is ...

I think the problem is a fundamentally misunderstanding of how to use the current() function. The current() function returns a ''node''. Thus, my:Employee[my:SomeNode] is an invalid statement and will not give you a valid result. You need to do something with that node that gets returned by the current() function. That is why my:Employee[. = ...

I am unaware of anything in a resource kit to do this. The only setting I know of is in the Tools | Form Options dialog. This prevents users from getting into the designer while editing a form, but does not prevent, as you've said, users from right-clicking the XSN or XSF file and choosing Design.

Great! Glad to have been able to help!

Is there a namespace on the IdNumber field?

When you use the rule to populate the other fields, you might have missed the ''Filter'' button. You need to use this so that you select the correct row (based on the value in the drop-down list box) so that you populate the fields with data from the correct row.

It initially appears that in this particular case, the reason is the long string of asterisks which the browser doesn't know how to break into separate lines. Thus the text falls off the edge of the page. I tried making the page landscape for printing, and still lost some text. I imagine I'd have to do a custom page for printing. Another option ...