Hi MaryAnn

Do not use a variable ("editing") to control button enable/disable. Use individual form properties (myform.editing). Then on GotFocus on the form, refresh those controls which could be changed by myform.editing.

>WHERE do I put WHAT to get the main screen to reflect changes in my "editing" variable so that it will enable the Save and Cancel buttons? I've tried putting "show get msavit" and "show get mcancel" (and even a general "show gets") in several different places like the ReadActivate Event and ReadShow Event of the main screen (form) and in the Unload Event and Read Deactivate of the "child" screen (form) . What is the Problem? Original explanation is below:
>
>Converted 2.6 app (which runs very well in 2.6) has several screens that work well together. Have main screen with menu options that bring up more information (more screens) regarding a product. If a change is made on one of the 'child' screens have a variable 'editing=.t.' then when the user leaves that screen, the main screen disables most of the command buttons except the save (savit) and cancel (mcancel). Since converting to Visual 5.0, if a change is made, upon returning to the main screen, it doesn't see that editing = .t. and does not disable the buttons or offer the enabled 'save' and 'cancel' buttons.