If it's a global var, why are you sending it as a parameter?
Wouldn't the procedure have it available already?
Also, is the parameter name the same as the global var? If so PARAMETERS makes it private, which may kill it; LPARAMETERS makes it local, which will kill it.

>Hi,
>
>In VFP3 as well as in FPW26 it seems to be the case that if I send a global variable as a parameter to a procedure, that global variable is dies.
>I have the UDFPARMS set to VALUE and I thought that the procedure would not be able to modify the variables used to send values to the procedure, and even less able to kill it.
>
>If I have missed something it would make life a little easier...