As Rip Ryness said, it's not a bug (at least I don't see it that way). In your function, you could have just prefixed your variables with m., not in the LPARAMETERS line, but in the "body" of the function, such as:

lcVal = Alltrim(fGetVal(txtString, '5', 'C', 100)) - <b>m.</b>nDec

It probably would be a good idea to be consistent and to always use the m. prefix when refering to memory variables to avoid this little problem.

---

>I had a very strange situation happen to me the other day, and while I've corrected it, I'm wondering if anyone else has run into teh same thing. It appears to be a bug in VFP - I'm using VFP6 with SP5.