Karen,

There's nothing wrong having a file with the name m.txt

(1) We're not talking about variables, and
(2) Even if we were, there wouldn't be any problem either


Don't let them confuse you

_________________

>Well this sounds ominous.
>i see what you're saying Koen and by all accounts what i am doing is declaring txt a vairable.
>
>on the upside so far i have not had any problems with it - opening, creating or saving - and that's going back 15 years.
>i don't have many occurrences of the coding that calls on what you describe - and those seem to work without issue as well.
>
>On the downside - i just checked and i have 2165 occurences of m.txt in my programs. i could change them enmass with the find and replace program i am using - it would take 2 minutes - but i am leaning towards if it ain't broke don't fix it. sometimes those enmass changes create some unexpected experiences.
>
>I am wondering what vfp is actually interpreting in m.txt to overlook this blunder.
>set alte to m.txt ----- could it be storing txt as a variable each time then overiding this with what I am actually intending, or could it be following the initial logic in the 'set alte to' and not making the variable connection at all.
>
>Now you have me worried!!!
>
>k
>