"Overflow" error running macro

[malex0012]

I have a MS ACCESS macro that executes over 30 queries which updates a specific database table on the MS SQL server. The macro was developed by somebody who is no longer with the company. It has been running smoothly for several months now, but today it spit out an error message "6 Overflow". I do not have any idea what this means.
Does it mean that query #6 did not finished?
Is it running out of buffer memory that enables it to update the actual table that is linked to MS SQL server?
Do I need to have an ACCESS admin reset some parameters on the ACCESS database that I'm using?

I desperately need help. I need to be able to update our SQL server database table daily, but today's job had this problem.

Thank you for anyone who can help me.
Ming Alexandrovich

 

[malex0012]

I would like to add that the macro I was running does not have any calculations in it. It simply inserts and updates SQL server tables.

I was browsing some of the queries posted on the forum for similar issues and I found that Overflow error results from mathematical calculation errors.

So my error maybe different.

Thank you.

 

[spikepl]

"Overflow" can also come from inapproriate variable type. Most often, when trying to stuff a number which is too big to be Integer into a variable or field that should have been Long.

 

[malex0012]

Thank you spikepl for the reply.

I need to isolate the query where the error is originating from.

Currently, the error handler code is this:

Error_Handler:
MsgBox Err.Number & " " & Err.Description

Can I update it so it will display the query name and table name where the error message is coming from?
It will be a nightmare to wade through the 30 queries that it currently runs.

Thank you.

 

[spikepl]

disable the error handler and let the code crash. Or for debugging line by line follow Debugging Tiops here: http://www.access-programmers.co.uk/forums/showthread.php?t=149429

 

[malex0012]

Thank you very much spikepl.
You've been most helpful to a newbie in ACCESS.