Hi Jim,

>I believe we are saying the same thing. A variable has two properties in this area, visibility and scope. Scope defines the lifetime of the variable and visibility defines what routines can address the variable.

><strong>Var Type		Visibility		Scope</strong>
>PUBLIC			Everywhere		Creation to release or quit VFP
>PRIVATE		Creator and below	Creation to Release or creator ends
>LOCAL			Creator only		Creation to Release or creator ends
>

Exactly, but you are reasoning the PRIVATE's visiblity is a result of the scope: if the creator ends the variable is out of scope and the visiblity never end extends to the calling programs. I agree with that.

But what about while the variable is in scope? Your reason doesn't say either way, and it is tested and shown using the combo box of the Locals window to say that even while in scope, the visiblity doesn't extend above the creator.

So this is just an echo: There are two seperate differences between PRIVATE's and PUBLIC's, and that this is not relevant because it can't be shown in code just the debugger (unless Paul shows me wrong :-), this is how it works.

I seem to be saying the same thing over and over so until I think of something else, I'm done :-)