> I think Geoff made the more correct design decision than I did.

I am pretty sure that your control originally operated the same way as
mine (because I seem to remember that I pretty much just copied what
you had :-). So either you were asked to update it sometime ago, or
you were sent an update and missed the implication.

> The control should not serve a dual purpose of allowing editing
> and inserting to be done. I agree that it should show the current
> data that is selected but that is the extent of it.
>
> Just my thoughts, feel free to request otherwise.

I must admit to being surprised when I saw this use. However now that
I have seen it used this way it makes me wonder if it can be made to
work fully. It seems to me that (due to the tiny amount of code in
the control) it would be almost as easy to make it fully functional in
insert/edit (and maybe search) modes as it would be to disable the
control in these modes. (Obviously it will never be able to be used
to automatically instigate edit/insert mode.)

As Nick suggested, it would be best setup with property control to
make it easy for a developer to select how the control operates.

If you are happy for me to try I will do so. I cannot see that we
will break anyones code, since it half-works at the moment.

Geoff Worboys
Telesis Computing