-
You are attempting to use VB-style Boolean values (i.e. Capital-T rue, and Captial-F alse). XML uses all lowercase: "true/false".
-
The safest way is to do it in code, as that can handle extended (foreign) characters. However, if you have those, you can also add them to the string in the translate() function.
-
Keep in mind that I don't KNOW that that is really the problem. But it sounds like it could be.
Zero is probaly not the right margin choice. That is saying that you want your printer to attempt to print right at the very edges of your paper. You need to find out what margins your printer supports and be equal to or greater than that.
In the ...
-
InfoPath does not filter out new values by default. Think of a scenario where you have a repeating table with a filter on the first column field. You select or type a value that should cause the row to get filtered out... how then do you finish completing the fields in that row? You don't if it is auto-filtered. This is a feature. You must ...
-
Now you can still use filters on secondary dom controls, however you must do them manually in the XSL in InfoPath 2003. For some reason that feature was disabled for secondary data sources--even though filters are fully supported.
-
Sounds to me like it is referring to the print margins. You'll find these in the View Properties dialog box.
-
Just assign the default value to the field to which the drop-down list box is bound.
I.e. if you bind the drop-down to my:field1, and you want the default value in a list of colors to be "Red", then make sure my:field1 is pre-populated with the value "Red". The drop-down will do the right thing.
-
If you are comparing in code, you should already know how to due this by converting both strings to lowercase.
In rules, you can do the samething with the XPath translate() function:
translate(my:field1, "ABCDEFGHIJKLMNOPQRSTUVWXYZ", "abcdefghijklmnopqrstuvwxyz") = translate(my:field2, "ABCDEFGHIJKLMNOPQRSTUVWXYZ", ...
-
What problem are you having? I just recreated a new form from scratch using the guidelines on the reply you referenced, and it works fine for me. I'm using InfoPath 2003.
-
Glad to hear you got it working with a simple fix!