>>Thanks all of you for your help first.
>>Nadya, I tried your suggestion:
>>copy file temp.txt to (m.lcFileName)
>>it works well. Then I tried to skip the "m.":
>>copy file temp.txt to (lcFileName)
>>it works too. Can you explain to me what does the "m." means? I tried to search it in HELP but failed to find it.
>
>Power,
>
>m. means, that it's a variable, not a field name. Basically, it's not necessary to preceed variable name with m. However, you never know, how somebody can name fields in his/her table. Say, somebody needs a field called tcName (as it was quite recently in one of Jill's message). If you name your parameter tcName and use it without m. prefix, field name would take precedance. That's why couple of months ago I began to use m. prefix everythere in my programs. Before I didn't pay attention to such minor detail. Also I believe, that style of one of my colleagues made an influence on me. One of my colleagues, whos programming technique and style I respect most among other contractors, uses them everythere, where needed. I adopted this idea in my style.
>

Just IMHO. Of course, it's a matter of personal style and preference.
On the other side, using m. it may be a sign of not effective enough naming convention for the variables and fields, or not following the naming convention. I personally use m. only in certain situations, for example when I use SCATTER and GATHER. or when I want to emphasize by some reason to whoever reads the program that it is a memory variable. Using m. everywhere, IMHO, is littering the programs with these "m." and is unnecessary.