>Alex,
>
>>Why is the cListObjEdit's bizobj swapped with the FORM's bizobj in order to accomplish the deletion? I don't see why the cListObjEdit container can't handle the deletion itself.>
>
>Actually, setting the CListObjEdit's bizobj as primary, allows reuse of the code that is stored in the form's Delete method.

Hola Doctor McNeish! Long time no see...

I had a hunch the change had to do with reusability, but then you come accross someone like me and reusability becomes shmeusability :-)

>
>
>
>Would removing the code from OnCancelFirstRecord() solve the problem?

I actually took it one step further to preserve the OnCancelFirstRecord's original purpose:

Change it's code to the following:

if ThisForm.oBizObj.lPrimaryBizObj
     ThisForm.Release()
endif

This way the form is released ONLY if we're getting to a user cancelling a first record on the PRIMARY bizobj only.

Hope you had a good thanksgiving! Say hi to Felicity for us!

Alex

Low-carb diet not working? Try the Low-food diet instead!