Hi Sebastian

If you are displaying the customer condition field in a grid, you will have to use a join to get the condition into the customer list view. When you select one in a data entry grid, you will have to update the condition text and the foreign key.

If you are using a data entry form, your customer data entry view does not need the join. The foreign key in the customer is enough to let you set a relation or use a seek to get the correct condition record. You would only have to update the foreign key.


>Hi, Thomas!
>
>Thank you for your reply!
>All you wrote is true - but a little bit beside my question <s>!
>
>I can follow your ideas about GUI (having picklists etc.) - but my question was: How can I deal with the lookup table data in such cases:
>
>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: ....
>
>Any suggestions?