THREADS - ESRI Discussion Forums

You are here: Home > User Forums > arcgis 9.3 release candidate forums > Thread Replies

ArcGIS 9.3 Release Candidate Forums

ArcGIS 9.3 Release Candidate: ArcGIS Desktop forum

Provide debugging options in the Field Calc...	Stephen Lead	May 26, 2008
Re: Provide debugging options in the Field...	Jeff M	Jun 05, 2008
Re: Provide debugging options in the Field...	Stephen Lead	Jun 05, 2008

Report Inappropriate Content • Top • Print • Reply
Subject	Provide debugging options in the Field Calculator
Author	Stephen Lead
Date	May 26, 2008
Message	This isn't specifically for 9.3 RC but is a general enhancement request. Could we please have some form of debugging added to the Field Calculator when in Advanced mode? At the moment the slightest typo will result in a generic and unhelpful error message - Error Running VBA Code - User Interrupt. Some form of step-through debugger would be really useful here, especially since it's usually not a simple matter to copy and paste code between the Field Calculator and the VBA Editor. Thanks, Steve

Report Inappropriate Content • Top • Print • Reply
Subject	Re: Provide debugging options in the Field Calculator
Author	Jeff M
Date	Jun 05, 2008
Message	This is a good enhancement. In our database we have some bugs/enhancements for better error reporting for specific cases. However, there was no general enhancement for better error reporting and debugging within the field calculator. For example, if you wrote something that generated a syntax error, it would indicate the line number (or highlight the line) and bubble up the VBA error message. I therefore logged NIM035911.
	Jeff M. Development Technical Lead (Desktop) User Advocacy Group (UAG) ESRI Support Services

Report Inappropriate Content • Top • Print • Reply
Subject	Re: Provide debugging options in the Field Calculator
Author	Stephen Lead
Date	Jun 05, 2008
Message	Thanks Jeff. It would be really useful to have something which at least indicated where the error was, especially since there's no code completion so you're never sure whether the problem is a flaw in your code or a simple typo.