On 6/10/26 11:19 AM, Rob Berendt wrote:
If by "more than one inherent key field" do you mean a key on an order
detail file by order# and line#? You just have to do it right. Instead of
putting the PRIMARY KEY on an individual column you put it at the end.
CONSTRAINT iim_pri_key PRIMARY KEY (Order_number, order_line)

Fascinating. Actually, the "CONSTRAINT iim_pri_key" part is optional, at least in DB2 on a Midrange box and it seems that Stefan's syntax would have worked, if only I'd set it off from the last field with a comma. And sure enough, I found an example (albeit *with* the CONSTRAINT <name>) in *SQL for Dummies* (which, so far as I'm aware is based on MySQL and M$ Access).

At any rate, the new tool I'm adding to QuestView hasn't yet balked at anything I've thrown at it.

--
JHHL

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.