Graig,

>>Concatenated keys are used in almost databases. I just want to know if it will be managed without problemns by VFP database engine.

>You're going to run into the same problems that you would in any other database...cascading changes to the fields that make up the PK. You'll also have to check for duplicates everytime. Again, this is not a good choice for a PK. You can use it for a regular key, but PKs should not be based on data entered by the user.

You're spreading the wrong info again. PK's can be based on data entered by the user and in fact while not always the best choice, it can be the best choice. Your perception of using generated PKs is controversial and there are a lot of knowledgable people who do think this is wrong (Joe Celko). I think you should point out that there are different thoughts about this topic and not only spreading the info where you believe in the most.

Why do I have to check for duplicates every time ??? If a PK becomes duplicate the DBMS will generate a error which can be handled quite easely. I dont see any problems arising here.

Also I don't see a problem with cascading updates. This mechanism is described in the releational model and therefore implies that PKs can be applied to intelligent keys. Most (R)DBMSs have good working solutions for appling cascading updates (after all cascading updates are not so different from cascading deletes). We've been discussing this topic before, but it saddens me that you persist in being so ignorant and naive....

Walter,