>>>Vlad, if the programmer was a Clipper programmer, he may assume that any parameter passed defaults to LOCAL not PRIVATE, as that is how Clipper treats variables. Therefore he was switching a LOCAL to a PRIVATE for some reason as I suggested in my previous message.
>>>
>>>Barbara
>>
>>So, in Clipper, params are LOCAL (is this the same LOCAL as in VFP?) and not PRIVATE as in FoxPro. That would make sense. I have no idea if the author was a Clipper programmer before, but it's possible since I found a PRIVATE CLIPPER in a procedure (the CLIPPER variable was not used anywhere else, only declared).
>>
>>I also don't know if I have the original version, if it was modified by somebody else, etc.
>>
>>Thanks Barbara! I think you solved it. A virtual beer will come by private email. :)
>>
>>Vlad
>
>Definitely a Clipper programmer, then. The PRIVATE CLIPPER is an old command used when you could run Clipper code under dBase III+ and was used internally.
>
>Yes, LOCAL is essentially the same. It made it easy for me to understand things like how parameters passed to INIT were invisible in other methods, since it never occurred to me they COULD be visible.
>
>Barbara

Thanks again. I just knew that everything has a meaning in this world. You also gave me the meaning... :)

Vlad