>>Peter-
>>If you ever do write your own framework, you should think long and hard before using forms that depend on the default datasession. IMHO, this scheme shows tendencies to do things the FPW 2x way, and not the OO way. Handling things like record pointer coordination should be handled via a forms manager or some other object set up for inter-form communication.
>
>Erik, you have a lot of company with that preference. You can be sure that I'll stick with private DS until long and hard thinking has convinced me to do otherwise.
>

Peter,

There is one situation where a private data session is advantagous, that is with a child fomr that needs to directly manipulate its parent form's data. If a modal form is called from a form with a private data session and the modal form has the default data session, then the data session that the modal form runs in is the private data session of the calling form.

Therefore you can create4 interfaces that might show summary information on the main form with subforms that allow the editing of the complete information. The subforms would be modal and would be set to the default data session so they run inside the data session of the calling form. For example you could create an address editing form that could be called from the customer, employee, and vendor edit forms.