> Secondly there is no READ EVENTS, instead he creates a login form that is modal and that stays up all of the time behind the other forms that appear. I was surprised to see that as I thought that the read events command was absolutely necessary in vfp. Can anyone tell me why you don't need it or why you might not want it?


The READ EVENTS command tells VFP to stop executing and wait for a user-initiated event. A modal form has its own implicit READ EVENTS. If all other application processing stems from methods called from the modal form, then the form is acting as the "FOUNDATION READ" (to use an old term that I have heard here and there :-)). This is a rather silly way to do things, IMHO, but it will work.


>
>One other thing I noticed is that on some of the forms the programmer will create a textbox and set the controlsource to a variable that has not been instantiated anywhere, let say it's called "m.lVar", then he'll set the value of that control to false. (m.lvar doesn't get declared anywhere in the program) Then elsewhere on the form, say in a click event of a command button, he would say:
>

If you bind a control to a variable that does not exist, the control takes the initiative of defining the variable and declaring it public. This is also a rather silly way to do things, because the scope and origin of the variable are not apparent. But, as you see, it works.