Hmmm...this takes us in a whole 'nother discussion area. Personally, since the intro of VFP, I have not been one for memvars. Therefore, by caveat, all my memvars are LOCAL in scope and I don't use a scope prefix. I almost always use the LOCAL keyword with a memvar list so, since the scope is explicit, I don't feel compelled to use a prefix.
>
>Actually, I think "l"is still te right prefix. (Am open to argument though). The LPARAMETERS statement in the form init creates a new local name for the variable. We then have actually two faces for he same variable. If I call the array something different in the init, the example still works. Even changing the contents of the newly named array in the form::init changes the contents of the original as well. Neither is the original array in scope from the init statement, nor the new one in scope for the calling procedure. I think that makes them both local.
>
>Hence "l" is the correct prefix.
------------------------------------------------
John Koziol, ex-MVP, ex-MS, ex-FoxTeam. Just call me "X"
"When the going gets weird, the weird turn pro" - Hunter Thompson (Gonzo) RIP 2/19/05