We help IT Professionals succeed at work.

Access DB reached count limit 32XXX "Overflow" error

Committo Committo
on
Hi - A client is using a MS access DB for quotes and whatnot..  there is an embedded integer that has a the above limit.  I am looking for a way to use the same front end - but create a new DB that would reset these counts - or a simple change that will stop the error happening.
Comment
Watch Question

Top Expert 2014

Commented:
Is the limit in a table/field definition or VBA code?

Author

Commented:
The limit I'm referring to is at this link.
http://www.databasezone.com/techdocs/acclimit.html

"Number of objects in a database    |      32,768"

Using Access 2007 if that makes any difference.
Top Expert 2014

Commented:
Are you saying that you have more than 32000 objects in the database?!?  Are you sure?

I didn't think you would get an "Overflow" error such a situation.

Are there a lot of temporary objects?  If so, we can work towards clean-up code.
Most Valuable Expert 2015
Distinguished Expert 2018
Commented:
It is more likely to signal a simple overflow in a variable or table field declared as Integer.

Change that/those field(s)/variable(s) to data type Long.

/gustav
Top Expert 2009

Commented:
I agree with Gustav.  It would also be a good idea to do a Compact & Repair, to remove any redundant temporary objects.
Distinguished Expert 2017

Commented:
there is an embedded integer that has a the above limit.
Change the data type to Long Integer if you don't need any decimal positions.  Otherwise, define it as Double.

You should not have to change the FE but if the BE is not Jet/ACE, you will have to refresh the link.  Jet/ACE tables automatically refresh.
Distinguished Expert 2017

Commented:
I answered the question.  Integers have a limit of 32xxx so the data type needs to be changed.
Distinguished Expert 2017

Commented:
Sorry Gus, I didn't read back far enough.  Please cancel my award and give it to yourself.
Most Valuable Expert 2015
Distinguished Expert 2018

Commented:
Well, it might be so, but who knows?

/gustav

Author

Commented:
The person that manages the DB ended up creating a new back end DB using the same front end..  This reset the numbers and stopped the issue
Most Valuable Expert 2015
Distinguished Expert 2018

Commented:
Reset? Sounds like the cause wasn't removed, and the issue will show its face at some time again.

/gustav