>>My concern is with the behavior of my Add and Delete buttons. When the form launches it appears to be in edit mode since you can directly edit data previously entered in text fields (the form is from the VFP Base Class and does not have any custom properties, i.e.,cEditMode[I know, I know I shouldn't use Base Classes]). When the Add button is clicked a new record is inserted in the Parent table and in the "FirstBorn" Child table. My problem is I am using very awkward means to add records on pages with only child/grandchild fields.
>
>I actually prefer my forms to always be in "edit mode". Instead of enabling/disabling controls I check GETFLDSTATE() to see if any changes have been made to the current record before I go to another record or exit the form

Yes, I can live with the "edit mode" too. I never had a handle on the "edit" button approach. --- When you check GETFLDSTATE() are you checking the field state of the records in parent table or the child table, or any/all table in the in the database?

>Why not let the RI take care of adding child records when you add a new parent record? The same goes for deleting a record, let the RI take care of it.

Won't this produce many blank child records. And if I'm not using a grid how do I add additional child records to the parent? Or for that matter, children of children?

I still don't follow the delete issue. If I can't pack the table how do I prevent the data from appearing on thr form? How can I delete child records without deleting the parent?

>You only need exclusive use of a table if you are trying to pack it.

Thanks,

--lincoln