Hi Bill,

I have a feeling that the other views you need to touch are not InitialSelectedAliases of their respective bizobjs.

In a case like this I would create a separate bizobj for any view that needs updating.

Then you can cascade changes by using the bizobj's postsavehooks or tie them to events on the form.

If there is a predetermined sequence of actions that must be taken upon the firing of a specific event, I suggest you follow Jim Weil's advice, and create an event object.

Good luck!

Alex


>Hi All,
>
>I have a design problem.
>
>The app in in MM vs 6 and vfp6.0
>
>I have a screen with 5 pages, each updateing a specific view. Works fine.
>
>On one of the pages if a specific field is changed I need to update the view normally related to the page AND I need to update a view tied to a different table. The 2nd update needs to be done after the normal view is updated and before I leave the page. I have tried a number of things and am unable to find the correct combination.
>
>I have set up a 2nd dataenvironment with the views needed for the 2nd update. I have set code in the 'postsavehook' of the bizobj (after changing the dataenvirenment) but get an error that says I cannot requery the view in the 2nd dataenvironment because it is within the original transaction.
>
>I have tried to tie the 2nd environment into the 'ischanged' method of the bizobj but it ends up in a 'DO' loop.
>
>The form 'deactivate' works, but it does not fire if the user closes the form before going to another page, so it only works some of the time.
>
>The bizobj 'deactivate' only fires when the form is closed and not when the page is closed.
>
>Any suggestions would be greatly appreciated.
>
>TIA
>
>Regards,
>
>Bill