>I feel quite stupid as I'm sure the answer is Dead Simple but, try as I might I can't get my head round this problem.
>
>I've just converted from 2.6 and I'm developing my first VFP application (5.0) - yes, I know 7.0 is available and I've got it but not yet installed! The advice seems to be that modeless forms are what one should normally use. BUT try as I might I can't get the module to transfer control to a modeless form after I've executed a "DO FORM". It just carries on executing the following code. In 2.6 you said "DO xxxxx.SPR" and the form appeared. What am I failing to do - or failing to understand??? Help please!

VFP is much more powerful than FoxPro in this aspect - every form can independently receive and process user input. This required a complex workaround in FoxPro.

Actually, code in both forms gets processed.

A method (say, Button.Click()) in Form1 calls Form2.

Several methods in Form2 get executed: Form.Load(), Form.TxtBox1.Init(), etc., Form.Init(), and many others more.

When there is no more processing to be done in Form2, the code in Form1.Button.Click() continues to be executed.

Provided you correctly set up a READ EVENTS somewhere in your program, both forms now wait for user input.

HTH, Hilmar.

Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)