Sergey (and Nancy),

I guess I've gotta do a better job of using the Queen's English...

the talk was about parameters and locals, etc.
My only point was that everything EXCEPT the parameters permissible within parens. in a FUNCTION statement had been discussed AND that these too were LOCAL even though the VFP7 documentation fails to mention this important point.

I had in fact double-checked Hacker's to confirm that this was correct before I sent that message. But I believe that the fact is an important one that belongs in the FUNCTION command documentation. (more below)

>>...and, to round it all out, there are the parameters indicated within parentheses after the name on a FUNCTION statement. These are implicitly LOCAL too,although I couldn't find this documented in the (VFP7) Help for "FUNCTION Command".
>>
>Ok Jim, You started this:)
>
>Let's take a closer look at FUNCTION Command in the help:
>
>1. No mentation about PARAMETERS statement or why it shouldn't be used here.
>
>2. From help "To distinguish a program file name with more than 10 characters from a function beginning with the same 10 characters in these two products, surround the program file name with quotation marks or include an extension after the program file name." Can somebody explain to me what does it mean? What two products?
>
>3. How would you call function usually? m.somevariable = Somefunction()? You would think so but help only says "When you issue DO with a function name, Visual FoxPro searches for the function in a specific order as follows: ...".
>
>4. The example instead of showing a simple function with parameters for some reason uses a custom object class.

I think that you're saying that there is lots lacking in the documentation for FUNCTION Command. I agree with that and, sadly, find that it extends to over 50% of the (new) documentation that I have visited to date (truly only a small portion so far). Much nicer format but far more omissions/errors/inclarities.