1

I have a need to store over 350 fields in a table and have this information readily available to display spatially. The problem is that access only allows for 255 fields. So the feature class that I am wanting to store all of this information does not have the ability to hold all of those fields..

Can you help me think of ways around this limit?

The only solution I can think of is to store all of my information in a big, long csv and then call out the information that I want at that time in a join.

The office that I am at is behind on the times and is still heavily using Access to query and store our data. We are WELL AWARE of the limitations and are on our way sometime in the next year to hopefully go to ArcGIS for Server and SQL server.

PolyGeo
  • 65,136
  • 29
  • 109
  • 338
forrestchev
  • 400
  • 1
  • 12

1 Answers1

6

Personal geodatabases--really anything with Access--have a ton of limitations. File geodatabases permit up to 65,534 fields per table/feature class.

It should be no problem to import your existing data to a file geodatabase and then make the changes/additions that you need.

Tom
  • 4,128
  • 1
  • 20
  • 38