Are you saying you issue the command:

do form MyModalForm to ThisForm.GridName.ColumnX.Text1.Value?

Not that I would ever do that, but since you are having problems, I would return the value to a local variable, then replace the grid control value with the variable value.

do form MyModalForm to lcReturnValue
ThisForm.GridName.ColumnX.Text1.Value = lcReturnValue

Does the Unload of the modal form look something like:

return ThisForm.SomeControl.Value

My guess is something that worked in 6 [that should not have?] got fixed in 7. It may be that you are setting the value in the grid control based on a value in a control of the modal form once the Unload of the modal form fires. Therefore you kind of have a deadlock where the modal form can not completely release and destroy itself because the calling form is holding a reference to one of its controls. Kind of like the old deadly data locking/editing/updating embrace.

>Hi All,
>
>I'm wondering if someone on the Thread could try this test for me. I've found a problem with vfp7 and a modal form returning a
>variable into a grid column's textbox. Mainform is set a top level form with a grid displaying data from a table. In the valid
>event place some code that runs a modal form (within main) and pass a variable to be returned and assigned to the textbox's
>value. The lookup (modal form) uses a list box and when a selection is made it is released and returns the variable to the
>grid in the mainform. What I've found is that when the lookup returns the variable it displays in the grid but the grid loses focus
>and locks up. The same exact code works in VFP 6.0 just fine.
>
>thanks in advance,
>
>Don