Lookup field selection difficulties (All databases tables having single field primary keys possible?)

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Lookup field selection difficulties (All databases tables having single field primary keys possible?)

Christian Carlow-OFBizzer
Does anyone know of a way to handle selecting a record from Lookup
control record lists when the record identifier is based on more than
one field?  For example, I need the ability to select one OrderItem from
a list of OrderItems associated with more than one OrderHeader.

The easiest way to be able to do such a thing would be to have a single
id field as the primary key for each OrderItem.  Doing so however, would
probably require significant effort to change the system to use the new
primary key.  But, wouldn't the system database be better designed if
all tables used a single field as the primary key and replaced
multi-field primary keys with constraints?

I also have the need to select a particular shipmentItemSeqId in a list
of multiple Shipments and face the same problem.

Has anyone a solution to this problem?