No, the short answer is you set up 152 parameters on the LPARAMETERS line and throw the error of your choice if you don't like PCOUNT().
On Wed, Nov 23, 2016 at 11:53 AM, Gene Wirchenko genew@telus.net wrote:
At 04:07 2016-11-23, Ted Roche tedroche@gmail.com wrote:
On Wed, Nov 23, 2016 at 4:39 AM, Paul Newton Paul.Newton@pegasus.co.uk wrote:
Microsoft Visual FoxPro 9 SP2 Help file, VFPX Edition v1.06 states
PARAMETERS ParameterList Specifies one or more variable or array names to assign data to. Use commas to separate multiple parameters in ParameterList. Generally, you can pass a maximum of 26 parameters; however, in some circumstances, you can pass 27 parameters.
Yeah, I'm pretty sure they cribbed that from the Hacker's Guide :) I remember testing that. That was the limit for VFP6/7, but VFP9 appears to have a much higher limit.
152 by my testing, but this is irrelevant. What practically everyone has missed is this is *NOT*, repeat *NOT*,about how to pass a lot of parameters. Using a parameters object is irrelevant.
Take a look at the title of the thread: Dealing with Extraneous ParametersIf a caller passes too many parameters to a procedure, how do you handle the situation in the procedure? The short answer appears to be that you can not.
Sincerely,
Gene Wirchenko
[excessive quoting removed by server]