>Thanks Gerald for the reference to the other thread on this. I noticed reading that thread that the person discussing the fact that he had been able to use 43 parameters was calling a PROCEDURE - DO program WITH parm1, parm2... rather than calling a FUNCTION - program(parm1, parm2...).
>
>This agrees with my finding.
>
>I also note that it is suggested that code be re-worked if more than 26 parameters are required - I agree with this, but sometimes you inherit code and are forced to go with the way it is written.
>
>Sergy also replied to me saying more or less not to count on being able to do this in any future versions of VFP, but to stick to the 26 documented. I guess that's correct, but I wonder if anyone out there with a more intimate relationship with Microsoft (than me!) could say whether these findings are something we can rely on (if we really have to) in the future?
>
>Chris

I suggest that you follow the Sergey's advise and stick with the documented limit.
Even if it is supported in the next release
(you will be fixed on this in the june beta), you cant know for the release 10.

If you can recode this part, do it!
The empty object is a good at this task, you can add (many) props to it and use it as param object.

HTH :)