Hi Pascal,

RI defined in a database in VFP is handled through stored procedure code that is generated automatically in the DBC. So, if you're not a fan of VFP stored procedures, it's not so good. What the RI procs do is delete or update child tables or bounce changes that may violate references and, maybe, create orphans.

I am inviting criticism here, but I simply refuse to use it. I have seen applications go into the mud speed-wise when cascading deletes, for example, were defined via RI.

>Recently when I started using an add-on that uses persistant relations, I've started using them. I was wondering as I didn't need them untill now what funtionallity they add to your database, except for the fact that these relations are proposed automatically when you create a view or a dataenvironment for a form (which I prefer to do myself ...). I know they're are used by the RI builder too (which I don't use ..), but what I want to know, are they only what is called meta data or does the database act different when they are defined ?