10062 Overflow during Document Check-in - Support

10062 Overflow during Document Check-in

From Support

Jump to: navigation, search
The following problem was Visual Basic related, and was related to a specific customer's custom scripts. It may/may not be applicable to your situation


If you have a question or seek clarification, please call Technical Support.

Problem:

Customer is getting an error message from the scripting engine that says "10062 Overflow." when trying to check in a document via RJS Imaging Scan Workstation.

Solution:

Checked the PreProcessExit procedure in their custom RJSIMGSCAN.BAS script. They were formatting their customer number as: Format(CInt(sReturnVariant(1)), "00000") in order to force it to have a minimum of 5 digits.

Changed this line to Format(CLng(sReturnVariant(1)),"00000") and it worked.

The problem was that the sReturnVariant(1) was defined as a Long so the size of the numeric being returned was too large to fit in a standard Int, thus causing the overflow problem. Check the variables being passed through the script for datatype mismatch.

This article has been proofread by Jordan as of 15:47, 9 April 2007 (Central Daylight Time)
Personal tools