Run-time error '6': Overflow on POS 2009/10
Joshua Hawkins_9188914
Member Posts: 2 Novice Member
Fresh install of Reckon POS 2009-10 on a Desktop running Windows 7 Professional 32bit. Upon launching the software I get this error - Run-time error '6': Overflow - the program then crashes.
I have tried the solution posted in the reckon support page which suggests reinstalling the software and then reinstalling in safe-mode.
I have also attempted to install this software on:
Windows 7 Pro 64bit - same PC
Windows 7 Pro 32bit - separate computer entirely
Windows Vista 32bit - separate computer entirely
Same error on all of the computers.
Has anyone had this issue? Seems like there is an issue with the .NET code.
Thanks in advance!
Regards,
Josh
I have tried the solution posted in the reckon support page which suggests reinstalling the software and then reinstalling in safe-mode.
I have also attempted to install this software on:
Windows 7 Pro 64bit - same PC
Windows 7 Pro 32bit - separate computer entirely
Windows Vista 32bit - separate computer entirely
Same error on all of the computers.
Has anyone had this issue? Seems like there is an issue with the .NET code.
Thanks in advance!
Regards,
Josh
0
Comments
-
Hello Joshua,
Welcome to the Reckon Community.
Open the POS Administrator and Compact & Repair the database. Then try again.
BTW, are you using an existing database file or a newly created one?
regards,
John.0 -
Hi John,
I have tried that but still the same error.
Tried with both existing as well as newly created database and get the same error.
Any other suggestions?
Regards
Josh0 -
My pos is not working Pos scan Run time error 6 Overflow So how can I fix0
-
Hi Socrates,
Check out the following KB article in relation to that particular error message -
Run-time error 6 overflow when opening POS Terminal
0 -
Hi Socrates,
The above fix provided by Rav did not work for us. We spent months and many hours trying to solve this issue.
In the end we found out that the database was the issue. It was corrupt. So we started with a fresh database and the issue was fixed.
I hope that helps.
0
This discussion has been closed.