WO2015
asked on
Access Run-time error '6' Overflow
Hello,
I keep getting this error in an automated access database that I have been running everyday for years without issue. I have no idea what it means. When I click "Debug" on the popup it takes me to the Modules Code and highlights a line. "NumDays = DateDiff("d", Today, INT_DATE)". These Modules have never changed and are provided by our software company to figure out financials. This has been working for years and all of the sudden it is not. It run on a Server which has also not changed. Please advise if you need any fixes, thank you!
I keep getting this error in an automated access database that I have been running everyday for years without issue. I have no idea what it means. When I click "Debug" on the popup it takes me to the Modules Code and highlights a line. "NumDays = DateDiff("d", Today, INT_DATE)". These Modules have never changed and are provided by our software company to figure out financials. This has been working for years and all of the sudden it is not. It run on a Server which has also not changed. Please advise if you need any fixes, thank you!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
you may have define NumDays as Integer
integer range is -32,768 to 32,767
you may be getting results beyond those range
change the definition to
dim NumDays as long
integer range is -32,768 to 32,767
you may be getting results beyond those range
change the definition to
dim NumDays as long
First of all, Today isn't a built-in VBA function, so unless it is a variable, it must be a mistake. In fact, instead of Today you can write Superaladocious, and you'll get the same result.
Secondly, it is highly unlikely that INT_DATE should hold a value of 1/2/1900.
Basically, this means the code must be debugged to find out where things went southward.
Secondly, it is highly unlikely that INT_DATE should hold a value of 1/2/1900.
Basically, this means the code must be debugged to find out where things went southward.
ASKER
I didn't want to edit the code itself. This module was developed by our software company and has always worked. What I did do was find the account that had that 1900 date. Changed it to the correct date and it works! Thank you!
ASKER
The pop up says: INT_DATE=1/2/1900
I assume that 1900 is a problem?