Re: next question determining which columns are in the primary key

I recommend you avoid this, too. If the primary key is composite, store references to it in multiple columns.

If there's agood reason not to do that, then define a surrogate key for the original table, and make your foreign key references to the surrogate key instead of to the composite key.

Fraser Boswell wrote in message <37CD19F8.CC93B247_at_spamme.ed.ac.uk>...
>In that case I want to store the primary key of the table in a field, each
part
>of a composite key delimited by a comma, so I can split it up later and
seek the
>required row.
Received on Sat Sep 04 1999 - 11:41:20 CDT