Mike,

I have never seen a readonly cbo in any other application. I have seen disabled cbo's, but never one that could be dropped if the user could not change the value. So IMHO you should just Enable=.f. if the user doesn't have the correct access level. They probably shouldn't even be able to see the list of possible values.

Conditional instantiation, or even just conditional visiblity isn't really that much more work than what you've probably done already.

Workarounds may seem truly annoying, but sometimes they are necessary. The good thing about OO is you can embed the workaround in a low level class and never worry about it again.

>EG: I have a Combo on my data entry form, my field-level-security toggles the ReadOnly Property. It will be ReadOnly a some points and not at others depending on the user and there access. Removing a readonly TextBox, and adding a non-ReadOnly Combobox at run-time is not my bag.