>I'm obviously missing something very basic here.
>This is the nitty gritty - the event management that I can't grasp within vfp.
>
>I have two ways a user might enter the address book from other forms. Both take the form 'do form address'. One works as expected. When the user presses 'alt a' the program executes 'do form address'. The form loads and sits there waiting for user input until they 'quit' the form.
>
>The second one is activated in response to the user answering (affirmatively) the question 'add new address now?' from the validation method in the other form . This then also executes 'do form address', loads the form, activates the first page but then continues past the 'do form address' line without stopping to let the user do anything.
>
>I can vaguely understand that part of the problem is that for the 'problem' code I'm calling the form from within the validation method of another form. But I don't understand why that should be an issue.
>
>I've bodged around the problem by having the address form set itself to windowtype 1 if called from the other form's validation method and this works. But I'm sure that can't be the way it's supposed to be done!
>
>What is it about the way you call a form that determines whether or not it is 'read'? Nothing I can find in the help sensibly or intelligibly explains this behaviour.
>

I'm not sure I completely grasp our problem, but I think you are grappling with the issue of Modal vs Modeless forms. When calling a Modeless form, execution in hte calling procedure is halted and control is passed to the called form. Execution of the calling procedure does not continue until the modal form is closed. When calling a modal form, execution goes from the calling procedure, to the called form's load, to the init, to the show, to the activate, and then back to the calling procedure before control is ever passed to the user.

You can change the windowType in the init method according to your needs.

Does that clear anything up, or just muddle things?