Alessio,

What I tried to say is that it won't be allowed to have a #DEFINE for a variable WConstant, and "re-use" that by means of WConstant = "SomeValue".
I didn't try it, but as far as I know it just is allowed to do this, but all kinds of strangenesses occur.
So look in your programs for the WConstant variable, and look for some assignment command put in by accident (think of STORE too).

By the way, what is the constant value ? obviously some wrong value could cause problems (at a Replace etc.).

HTH,
Peter


>I'm not sure to have understood what u said.
>Anyway I'm sure i've not used the same name twice and if I define a variable in which i put the constant value it works.
>the fact is that I cannot explain why i cannot use constant in those cases
>---
>
>>>I included a .h files in a form, i do that everytime, but today i brought into an error :
>>>I mention a constant in a replace command (replace fieldname with Wconstant)
>>>but VFP gives me a sintax error, error which fades if I sobstitute the constant with its value.
>>>The same happened (today is my lucky day) in an IIF command, if I put the constant in the iif values VFP gives me the error "missing expression"
>>>
>>>Is it normal or there is some patch to fix that i suppose its a bug ?
>>>
>>>Thank U again
>>>Alessio
>>
>>Couldn't it be so that you defined the constant-variable again in the running program (WConstant = "SomeValue") ? (if that would be allowed anyway).