>Hi, Folks!
>
>What about dealing with lookup tables in a view based MM environment, e.g. Customers table CUST with a foreign key to a billing condition lookup table BILLCOND?
>
>This question has two sides:
>1. How can I display the the real world billing condition value from BILLCOND instead of the foreign key value in the related foreign key of CUST?
>2. How can I deal with selecting an alternate billing condition due to the user in the customer form?
>
>Ideas:
>Idea A: I can inlcude the lookuptable in my cutomer view using a JOIN - but what about dealing with selecting another billing condition?
>Idea B: I can create a separate view parameterized with the contents of the foreign key field - but how can I synchronize the two views?
>Idea C: I can create an unparametrized billing condition view and establish a relation between this view and the CUST view - but I have to handle the relation stuff (i.e. creating on-the-fly-indexes etc.).
>Idea D: ....
>
>How do You handle such stuff?
>
>Any suggestions are very warm welcome <s>!

Hi Sebastian,

In such a case I usually build up a combobox with a parameterized view as its source, and requery it when passing from record to record.

If I had to display some or all customers in a grid, I would do the same, plus have the text value from the billing condition (using a join). I would display the text field for all rows, except for the selected one, where the combo would be available.

José