>It is an existing method of a class and we're normally passing everything as parameters. Here is the current declaration of this method
>
>

>procedure ValidatePass(tcSalesPoint as string, tcOperator as string, tcPassTable as string, ;
>		tcWhichKey as string, tcPrefix as string, tnPassNo as double, tcDptCatItm as string, ;
>		tnNumVals as integer, tcPhysLocation as string, ttScanDateTime as datetime, tnParentNo as double, ;
>		tcNoTrans as string, tnScanNo as double, tnSiteNo as integer, tcScanNo as string, ;
>		tcCheckpointName as string, tcCheckpointValue as string, tlTrickle as Boolean, tyPrice as decimal, ;
>		tnTransNo as double, tnCreatedPassNo as double, tcAutoSaleDCIs as string, ;
>		tlFromScanner as Boolean, tcPassNo as string, tnBenefitID as double, tcMbRedemptions as string) as string ;
>		helpstring "Process a validation for a passholder record including updating record and recording log entries."
>	

>
>So, normally I would add an extra parameter (as I need to add tnExtraDays parameter). I guess I have no other choice but to create nExtraDays property of the class and use it instead and re-set in each call. The problem is that I already coded another method to use parameter and for consistency I think I'll change that method as well to use that new property.

If it is contained, such as a class calling a method of its own, I would use parameters. This usually does not evolve and are usually limited to a few parameters. For client applications, calling those class public methods, I would pretty much always use class properties.