The Parameters() function is the one that resets. PCOUNT is preferable because it doesn't do that. You're right not to call the function multiple times for performance.

>Tore
>
>I haven't come across this problem often but I'm pretty sure that sometime in the past, once processing had started in a parameterised proc/func, PCOUNT() had lost its result and could not be relied on. For this reason, if I'm testing for the no. of params I always store PCOUNT() toi a var first thing.
>
>Now I don't know whether this has been fixed with later SPs, or indeed later versions, but just a precaution I take. Besides, the purist in me doesn't like calling a func several times
>
>>

>>lparameters cPar1, cPar2,cPar3
>>do case
>>  case pcount()<3
>>    cPar3='mydefault3'
>>  case pcount()<2
>>    cPar2='mydefault2'
>>endcase

>>
>>>Let's say I have a procedure that is expecting 3 parameters, but sometimes only 2. They should all be character. Is there a standard that others use that would run through some validations, checking type, pcount, stuff like that? Want to make the project I'm working on as tight and error free as possible. Here is an example:
>>>
>>>

>>>******************************************************************************************************
>>>FUNCTION Procedure_Locked
>>>******************************************************************************************************
>>>
>>>	LPARAMETERS tcProcess, tcLockUnlock, tcUserID
>>>
>>>