At 09:37 PM 12/04/2005 +0200, you wrote:

>At 11:04 AM 12/04/2005 +0200, you wrote:
>
> > I use a TwwDBGrid with programmatically filled columns:
> >
> >with MyGrid.Selected do
> >begin
> > Clear;
> > Add('DEBITOR' + #9 + '14' + #9 + 'Deb' + #9 + ');
> > Add('ARTICLE' + #9 + '16' + #9 + 'Article' + #9 + 'T');
> >end;
> >
> >I use a TwwSearchDialog with the same selected property.
> >If I use the SearchDialog and search for a not existing value then an
> >error shows up with "Column unknow DEBITOR".
>
>Correctly, since your DEBITOR field is not a database column.
>
>gh: Ok, but an existing value is no problem. How come ???

I don't know how those controls work, but a reasonable guess is that they
search the buffers first and then query the table if the search match is
not found. The "field not found" error then occurs when the search query
is requested.

>gh: The problem is that the fields in the join query has the same
>name, So I need to distiguish them in the appointment of the
>Selected-property. If I don't alias them myself, then the field-editor
>does. I suppose renaming the fields in the database is the only
>option?

It's not the only option and it's surely not a good option. A clean
solution is to make a view out of your joined set. Searches, filters and
KeyLinks then work "out-of-the-box". You can then either provide triggers
to make the view updatable, or you can write custom DML for the updating
operations.

Helen