>I apologize for being dense, but these explanations just baffle me. I do not >understand why anyone thinks the ReadOnly property should only be respected for a >dropdown combo or why this is a good idea. I have designed my class to workaround >this "design feature" so it is really no longer an issue.

>My particular issue with this is I need a control that is a dropdown list and not a >combo because the users are not allowed to add additional values to a particular >list. However, not all users have edit privileges. So I need a dropdown list whose >ReadOnly property can be linked to a user's priveleges. Since we do not have that, >I have just disabled the list for ReadOnly users. If it is a combo, I make it >ReadOnly.

Mark,

I agree with you--this is a bug, and the surprise one gets at experiencing this bizarre behavior is part of the membership initiation into the "Brotherhood of the Combo" <s>. The idea that a value of a read-only control can be changed runs totally counter to what "read-only" means. Whether the style property is set to 0 or 2, the list of choices should either not be displayed or if displayed, any attempt to change the value should be ignored by the combo and the original value/display value restored.

John