>who has the table in its DE, and the child SEEKs the record for display and >manipulation. But VFP will not allow updates. (Private Datasessions, >optimistic table buffering). If the 'child' form was only dealing in one >value, I would just pass it back to the main for REPLACEing. Currently, the >only solution I see is to pass the values back in a concatenated string and >parse them back out to dates in the same routine that calls the form. There >has GOT to be a better way. Anyone? How about setting the child form's DataSessionID to the parent's ID? Just pass the parent's DataSessionID as a parameter to the child form, and in its Init use Para InheritedID_ln Set DataSession to InheritedID_ln ....and you'l probably need no separate DE for the child form.