>>>>I did the same thing. Although the details are slightly different, the technique is the same...."clear" the control if the user presses the delete key.
>>>
>>>Thanks for the sanity check. I was under a strong impression there was something simple instaad :)
>>
>>Another posibility would be having a blank value as a choice (e.g. original select would have a union clause). But I like this approach too. Perhaps, we can add this code to our combobox class.
>
>We've had cases where this union thing simply won't. I mean, it would work, but it would be dead slow on a couple of forms which are already pulling 40+ tables, and the combo I'm thinking of has a 6000 records table for a rowsource. Just creating a union with a blank record for that one would last some, and then it wouldn't work, because in this case there are four or five filtered indexes for this - and rearranging things to include four or five views or cursors (including one non-filtered) would create just a fine mess and further slow down, and would get us a problem of where to include the blank one - into each one or... well, simply blanking was the quick & easy way.

Dragan,

I agree with your reasoning completely. Actually, I was the first, who pointed to this problem with our classes and we had a brief discussion on this topic, which doesn't lead to any conclusion. I originally suggested to use Combo's right click to clean the combo having in mind the code similar to yours. My manager decided otherwise and he just went to all our lookups tables and add one blank record with empty value in a code field and as a description.

This is definitely not universal decision and didn't solve the problem, where we don't have this extra record and still want to clean the combo value. This problem is still unresolved in our classes. May be I'll raise this issue again in appropriate time (since now we're dealing with some other more important issues).

If it's not broken, fix it until it is.


My Blog