<snip>
For DDS replacements, I set the primary key to match the DDS, in order to
lessen the migration headache.
</snip>
I would tend to agree with that.
On a new system I would always create a primary key constraint.
However there are software products which never put a key on their tables
and always do it with indexes (in their case, logical files). Infor is
one. I truly believe that it's a standard adopted by someone who got
burned by something back on a S/3 and adopted that as a work around.
Infor never even specifies UNIQUE. So, yes, if you additions outside of
their programming interface (like conversions) it's quite easy to add
duplicate item numbers in the item master and such stuff.
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.