Walter,
What I meant by that is that VFP does not have automatic functionality built in to handle RI (e.g. Cascasde deletes, etc.) the way Access has or SQL Server 2000 has.

You actually have to add some code somewhere. Whether you do it with a builder that generates SP code individually for each table or you use the same RI SP code over and over that can be inserted at database creation time that reads an RI table doesn't much matter in the grand scheme of things.

>Larry,
>
>>No, I don't open the database and hand code the rules. I use the RI Builder from Effective Techniques.
>
>O.K. That explains. But your answer to the original question:
>
>>I do agree that RI should be coded manually (as that is the only way it can be done if VFP currently). However, I would not do it in PRG code, I would use stored procedures and triggers; hence, use a database.
>
>seems a bit misleading. Can we conclude that it is preferred to use some sort of RI builder that generates constraints in the database itself rather than program the RI in the application (which was in fact the question) ???
>
>Walter,