>>It works (just put the M in the Format property, and Option1,Option2,Option3 in InputMask), but it's actually far better to use anything else - dropdown combo, listbox, or even an optiongroup (not this time - you obviously have scarce real estate). The trouble with @M is that it's counterintuitive, and it doesn't provide for a visible list.
>
>Good explanation - I was thinking along those lines too, but not as coherently as you :)

Coherent explanation? Me? I must have been completely away from my own influence for a while :)

I used the @M in FPD on quite a few occasions, because it was just way easy to do and to put in little dialogues, specially with its small screen footprint - but then each time it required some explanation to the user. In converted forms, I'm usually replacing them with dropdown combos, optiongroups or even checkboxes, whatever suits the situation. End those don't need any special instructions for the users :)