Precision for Long Integer fields incorrectly reported as 10
Last Published: August 25, 2014No Product Found
Bug ID Number
NIM003510
Submitted
July 26, 2006
Last Modified
April 2, 2025
Applies to
No Product Found
Version found
9.2
Status
Will Not Be Addressed
The development team has considered the issue or request and concluded it will not be addressed. The issue's Additional Information section may contain further explanation.
Additional Information
We apologize that we were unable to address this issue within the current product support cycle. If the issue continues to affect your work in a supported release, please contact Technical Support.
Workaround
Workaround for a new feature class---------------------------------------------Create a brand new feature class, specifiy data type as long integer and set the precision to 10.Workarounds for existing feature class-----------------------------------------------i) Create a new field from the existing feature class, set data type as long integer, precision = 0, this should hold up to 10 digits. orii) Create a brand new feature class (e.g. FC_New), specifiy data type as long integer and set the precision to 10, then import the existing feature class's (e.g. FC_old) schema to the brand new feature class(e.g. FC_New), then uses 'Load Data' to populate the attributes and delete FC_old.