OK, (I'm learning here), I thought (from trying to interpret the manual) that
if you hide the form, it is no longer active....'
The reason I was forced to try modal (it worked when it was modeless just
fine) is that my instructions were to add my newly created VFP application to
a previously created (by my predecessor) 2.6 menu with READs. I changed the
READ to a READ EVENTS, but when the menu fired up my new app with modeless, the
logic fell right through the forms and returned to the menu. So, I thought
the modal forms would work better. At least it now doesn't fall through, but
now I have the freeze up.


>Tom,
>Actually, I'm surprised that the first form will do anything after Hiding form2 (debugger or not), since they are both Modal. I think the *standard* technique for what you're doing is to use Modeless forms.
>Mark
>
>>I don't know what to call this problem really, but I can hide a form
>>and show another form, then when I want to return to the first form, I hide the second and show the first, but right there the debugger pointer stops.
>>
>> The controls still respond to the mouse (like Next and Previous buttons), but the step by step doesn't show anymore on the debugger.
>>
>> I have tried it with Read Events on and off with no difference shown. Both forms are window type modal.
>>
>> Any ideas of what I could try? I took the code out of the Click method and put into a PRG procedure (and call it from the Click method):
>>
>> PROCEDURE hide_and_show_1
>> form1.hide()
>> form2.show()
>> RETURN
>>
>> PROCEDURE hide_and_show_2
>> form2.hide()
>> form1.show()
>> RETURN
>>
>> I have tried putting a 1 in the show [such as form2.show(1)] with no difference.
>>
>> I am using VFP 5.0 with Service Pack 3.
>>
>>The crazy thing is, this used to work fine, but now it won't.
>>
>> I just don't know what else to try. Or, what is the possible problem.
>>
>>Thank you.