RE: Embedded SQL, first steps

Always good to check for the exceptions.  Good work.

Wonder what a simple CHAIN does if there's duplicates?  Could cause some 
real issues if you're chaining to one record and it's the other record 
always getting the updates.

Here's a false assumption from one package:  BPCS.
Let's have no keys on the physical file for the item master.
On any logical based on this physical let's have no UNIQUE keyword.
Let's ASSUME that only new companies will use our software and that all 
maintenance to the item master will come from our item master maintenance 
menu option.  There will be no conversions from existing packages allowed.

Now, in the real world someone is rightsizing from a PC based package. And 
the PC based package has a few duplicate item numbers.  Or, someone mucks 
up consolidating a few divisions.  Now you have duplicate keys in the item 
master.

One of the falsehoods of doing all data integrity via programming and not 
letting the database do any of the work.

Rob Berendt