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?