>>2. In general, you should set relations for your tables by customer_id.
>>After entering the customer_id you can perform the SEEK customer_id in
>>Valid event for the customer_id field, and then refresh the form.
>
>I would disagree on this point: the relations should be set by customer_unique_id, which is generated automatically in the DBC. The user can never modify this value. This gives the user the freedom to change their customer_id as they need to, without destroying all the other information which uses customer_id for a relational key....
>
>All IMHO, of course. :-)

Garrett, you are right, that's what I do in my app, but it just a basic idea, with no details in particular. :)