[email protected] wrote: > I have a program, that has the following code at the top: > > > PRIVATE plValue, pcMessage, pcZipFile, pcDestDir, plZipIniExists, > pcCurDir, pcTmpFiles, pcLogFile, pcDrive, plOK, crlf > LOCAL lcError, lcSys16, lcProgram > lcError=ON('ERROR') > plOK=.T. > *- Trap all errors - will exit proram on any error > ON ERROR DO ErrorLog WITH ERROR(), MESSAGE(), PROGRAM(), LINENO() > > > > Program continues on from here. The above are the only variables used in > this program. In the only subroutine ErrorLog, it has 5 more. > > That is way less than 65,000, which the help file is the max number of > variables. > > A little more details... > > The program runs fine, no errors in the development environment, the "Too > many variables" error occurs only in the exe. > > In the ErrorLog subroutine, I write out the details of the error to a text > file, but the file does not get created, so the above error is not being > trapped?? > > Any ideas out there? > > TIA, > Mike
Is there any recursion that's perhaps looping and hitting this ceiling? -- Mike Babcock, MCP MB Software Solutions, LLC President, Chief Software Architect http://mbsoftwaresolutions.com http://fabmate.com http://twitter.com/mbabcock16 _______________________________________________ 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 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.
