Gene, I'd still use the Parameter object as a preferable solution but if you have to have parameters then why not have ONE parameter, that being a string with "|" delimiters for each parameter. In this way you could also have named parameters so that order would become irrelevant i.e
|Width=100|Length=20|Name="My_Name"| The only think to make sure of here is that there are no spaces in the parameter so I'd preprocess it and substitute "_" characters. Dave -----Original Message----- From: ProFox [mailto:[email protected]] On Behalf Of Gene Wirchenko Sent: 23 November 2016 19:30 To: ProFox Email List <[email protected]> Subject: Re: Dealing with Extraneous Parameters At 09:01 2016-11-23, Ted Roche <[email protected]> wrote: >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(). Well, no, because if someone passes 153 or more parameters, VFP throws "Allowed DO nesting or expression evaluation limit reached." It is turtles all the way down, and the last ones snap. [snip] Sincerely, Gene Wirchenko [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
