Some time ago, we sent out an update which applied numerous data base
constraints to the application. Specifically, many date/dollar/quantity
column values had a Not Null constraint added, Foreign Key references, etc.
The utility would look for any existing errors, notify the user to correct,
and exit. If there were no existing errors, the new constraints were added. 

A few customers ran it multiple times after there were no errors (our
mistake for not preventing this). The Not Null constraint is not duplicated
but the "Foreign Key References Tablename" is duplicated. The application
works OK, but I'm sure there is additional overhead and I am looking for
the best/easiest way to look for and remove the duplicate constraints in a
data base.

TIA,

Dennis
*****
Dennis Fleming
IISCO
http://www.TheBestCMMS.com
Phone: 570 775-7593
Fax:   570 775-9797

Reply via email to