Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Allowed DO nesting level exceeded. 3

Status
Not open for further replies.

CDavis

Programmer
May 5, 2000
155
US
With VFP9 I receive the following error when trying to build the project into an executable:

"Allowed DO nesting or expression evaluation level exceeded".

(All elements of the program work fine in the Development Environment.)

The build process does not generate a .err file to help narrow the source of the problem. Help for the error suggests the following:

"To exceed the current limit of nesting levels, change the number of nesting levels by including the STACKSIZE setting and the new limit of nesting levels in a configuration file to use when Visual FoxPro starts up. For more information, see Special Terms for Configuration Files."

Rather than change the limit, I prefer to identify the source of the problem and modify the program design.

Let me know if you have any suggestions.

Thanks in advance.

CDavis
 
I'm not sure about the coding syntax here. I think that it is part of the _GDIPLUS class and so assume it is correct??
I was misreading that error message and you're absolutely right. One thing you might want to check is whether or not gdiplus.h is located in your ffc directory. It may be erroring out on those preprocessor calls because it can't find the h file.

Regards,
Jim
 

Mike Yearwood,

It's somewhat a matter of preference. In terms of sharing bits with different projects, it's a no-brainer.

Well, I agree.

It's just that, as a matter of preference, I copy over all identical bits of code into a separate directory for any new project, and don't share it any longer, unless absolutely required. Sometimes they go different routes from this point on, and acquire their own changes.

I do have a few UDFs into their own .PRGs shared by several projects - they are required to be absolutely identical - but that's just a few.
 
Scott--I'm pretty sure Jim Winter is right and the problem is related to the include file. Make sure the GDIPLUS class is pointing to the right .H file and that the pathing is correct.

Tamar
 
I happy to report that the star worthy tip from Jim provided the solution.

The GDIPLUS.h file was not being found by the project manager. After correcting that I was able to get through the build. I still had a number of other errors that were thrown but at least now I get an actual error report and can deal with them.

Thanks again to everyone for engaging in the conversation. I may be able to incorporate a number of the ideas that were presented to improve the project.

CDavis
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top