>Thanks for all the PRB references in the KB. Even though the behaviour is documented, it is still a bug, IMO, because the behaviour is not even consistent.
>
>Well, I for one, hope that they do not change this because I rely on this in order to have my drop down list in a grid class work < s >.

So you are saying that if a dropdown list could be made read only, it would no longer work in a grid? That sounds like a bug to me.

>If this had not been documented (by design) I would never have built classes to take advantage of this behavior.

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.