Hi Robert,

That is interesting to note for reference. I am not sure why it would matter if there are not any child business objects, but we know there is additional code wrapped around that registration. Thanks for sharing the solution you found.


>Hi Tim. I made a couple "Simple" changes to my form and it now works as expected.
>
>********************************************************************************************************************************************************
>Instead of registering the _employees BO as the primary I registered it as a "Typical" business object.
>
>In the click event of the "Cancel" button I added "Me.Cancel(Me._employee)".
>********************************************************************************************************************************************************
>
>I searched for an employee record and got back "N" results. Added a new record and decided to "Cancel" that record and all is fine. Seems like the issue is somewhere in the chain when _employees is registed as a "Primary" BO.
>
>Thanks.