For those following this thread, the COMPILER accepts at least 1024 parms without complaint. I suspect, from a compiler perspective, the max number of parms is limited by the max statement length of 8192 chars. (Is this limitation still 8192?)
Without customizing the config.fpw's MVCOUNT, MEMLIMIT, or STACK settings, the max number of command line parms I can use AT RUNTIME is 128. Defining more command line parameters results in an "Insufficient stack space" error. Any suggestions on how to configure VFP to accept more than 128 command line parms? (for the motivation behind the need to work with lots of command line parms, see original post below) Malcolm <snip> VFP 9, SP1: Is there a max number of parameters that can be passed to a VFP app? I was under the impression that the max number of parms we could pass was limited to 26, but in doing some testing, I was able to create a main VFP executable with 720 parameters. Was the max number of parms changed in a recent version of VFP? Motivation: I have a VFP utility that accepts files dragged on to its shortcut. Prior to asking this question I had been limiting the max files (command line parms) that my utility could handle to 26. It sounds like my real limitation is the max length of a command line vs. the number of parms my app can accept? Does that sound reasonable? For those interested in the max length of a command line, see the following: <http://blogs.msdn.com/oldnewthing/archive/2003/12/10/56028.aspx> </snip> _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech ** 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.
