I have been running into problems with using relationships that deal from parent to child. In other words if I am on a record in a parent table and then VFP automatically shows the records in the child table. This works great for me except if there are no child records that match. In this case the last record in the child table shows even though it doesn't match.

Anyway, I have come to the conclusion that anytime I want this behavior I should use views which seem to work alot better. I have been asking alot of questions lately regarding generated pks and intelligent keys, composite indexes and single field indexes. I have also come to the conclusion, with alot of help from you guys, that I am going to use generated pk's in my child tables rather than intelligent keys like acct# etc. I do however need relationships then so that as I move through a child table the corresponding parent table has the correct record so that I can get pertinent information.

I am thinking about not using persistent relationships in the database container but instead...have a method in all of my forms where I can set temporary relationships for each form. Some of my tables can be quite large and there could be child, parent, grandparent and great grandparent relationships. Is this a wise scenario to be following? Is there a reason why I wouldn't want to be setting these temporary relations all over the place relating a child table to a parent table?

Thank you guys soo much,

Paul Acton