I'm using ArcGIS10.4.1 Desktop. A coworker was adding a field to a shapefile, specifying short integer. When she went to properties of that field it says it is a long integer. When trying to use the Simple Data Loader, the field types must match. I need the field to be a short integer but it comes up as a long integer.
I've tried adding a field to a different random shapefile and it also says Long integer when I specified the field to be a Short.
Thank you Adrian. That worked. I still wonder why adding a short integer to two completely different shapefiles creates a long integer. I sent a message to a friend in Utah and she had the same issue, adding a short integer to a shapefile for her created a long integer.
Rachel, I am wondering if the shapefile only had one kind of integer and that was just the 'long' variety. Maybe when the geodatabase came around, then it was introduced with more than one type of integer.
From digging around, I found this old article on when to use a shapefile, etc.
It looks like that the long and short integers in a shapefile (dBase format) are just "numbers". Same goes for float and double (they're both "float").
So maybe it's best to stick with geodatabases for things like this.
This link will jump you straight to the comment:
Interesting behavior in 10.3.1.
Just to be neurotic about it, here is Lance's copied and pasted comment (it's great info):
What you are seeing is a change to the behavior of dBase/Shapefiles introduced at 10.3.1. Normally a Short Integer can hold numbers from