Re: DBLookupComboBox question

> If this hack brings some new idea
> what you could try to do, then that's fine. Yet if it is
>garbage that
>won't fit to this situation, then it's garbage anyway<g>.

Cool. Code, even if it doesn't compile, is always useful -- it makes it
clear what you're trying to say...

I don't think the problem is strictly a display problem. When I select
an item from the list, it doesn't even save the corresponding integer.
What I expect is that it would display the item (recordName) that was
selected, and then use the keyField and dataField to save the recID to
table2.

If I make listField, and keyField to point to recordName, and then
create a name field in table2, and set it to dataField, then selecting
an item from the list causes it to be saved to table2. But I don't want
to gratuitously save the name (and make my table larger) when all I
really want is the foreign key. I also don't want to clutter up my
code by doing it by hand (which is probably what I'll have to do).

Maybe this is a good time to learn to write my own components... :)

-Corinna

.