You are here: > ESRI Forums > arcgis desktop discussion forums > Thread Replies

ArcGIS Desktop Discussion Forums

ArcGIS Desktop - ArcCatalog General forum

Error running VBA Code:User interrupt   Mita Som Jul 10, 2007
Re: Error running VBA Code:User interrupt   Dan Patterson Jul 10, 2007
Re: Error running VBA Code:User interrupt   George Teachman Sep 07, 2007
Report Inappropriate Content • Top • Print • This Forum is closed for replies.    
Subject Error running VBA Code:User interrupt 
Author Mita Som 
Date Jul 10, 2007 
Message Pre-logic VBA Script Code ,I am using to calculate area,(Yes I am working w/projected co-ordinate system UTM),I get this warning
Error running VBA Code: user interrupt
Sometimes,it will throw me some 0s,sometimes big 11 digit number, and most of the times nothing but error message.Area field should it be "double" or it can be longinteger,Why I am getting error message????? Thanks in advance. mita
 
   
Report Inappropriate Content • Top • Print • This Forum is closed for replies.    
Subject Re: Error running VBA Code:User interrupt 
Author Dan Patterson 
Date Jul 10, 2007 
Message often the error is due to null geometries, so you should run a Check Geometry from ArcToolbox and a Repair Geometry if necessary 
  Geomatics, Carleton University, Ottawa, Canada 
   
Report Inappropriate Content • Top • Print • This Forum is closed for replies.    
Subject Re: Error running VBA Code:User interrupt 
Author George Teachman 
Date Sep 07, 2007 
Message I've been reading this thread (back to 2004) and have the same problem; but a different solution.

The field in question is defined as text 254 characters. When I invoke the field calculator from within a model, I enter the character string, such as FORT LEE. I get the infamous error. I put in the string 1047, no error. This got me scratching my head. I went through all the reported fixes, which didn't work for me. So as a last resort I put the string FORT LEE in quotes so it looks like "FORT LEE". It WORKED!

Now I'm wondering if the field calculator doesn't look to see what the field is defined as before it calculates. It appears to not like blank spaces in the input. To my way of thinking in a text field it shouldn't matter what I use as input. 1047 is text as well as numeric. FORT LEE is also text. I shouldn't have to tell the field calculator TWICE that I'm entering text.

I don't know if this will help anyone else out there. But it solved my issue. Albeit, it raises issues about ESRI's coding.

Thanks for all y'alls help with this issue.

George Teachman
US Army Environmental Command 
  George Teachman
NRCS Soil Scientist - USAEC