Don't think of this as "wrong", it is just "old school". Remember, a long time ago RULES were the only way to do this. So we all made rules for unique values. At some point (don't remember which version), RBTI instituted primary and foreign key constraints. And they were much faster than rules. But RBTI kept rules in there, and I still occasionally use rules for things other than referential integrity and uniqueness. So it's just a matter of being educated to know that the "new" way of doing things is better than the "old" way. That being said, rules still have the advantage of being easy to turn ON and OFF.
Karen > Ok, All I had done (probably wrong) was to tell R:Base that Invno must be > unique. It created the code. So, instead of making a rule that it needs > to be unique, I should turn that off, and make that index a Unique index or > Primary Key? I will try that. Stuff like this bugs me... it has been > this way for 10 years, now it is wrong. > > Thanks.
