Where are you PY???
Give me a chance dude.
I only initiated this yesterday and I do actually have a life (and a job) outside DB. Sometimes I can't even get to the code for a week at a time.
Let's start at the beginning. (No offense intended if you already know this stuff)
As Bots suggested, hovering the mouse over a variable is the best way to find out what is wrong.
The most common problem seems to be "overflow"
This simply means that the result of a calculation is too big to fit within the variable type.
Most DB variables are defined as "single" (single precision floating decimal) or "integer". Both of these memory types assign 16 bits of memory to hold the value. That is 1*2*2*2*2*2*2*2*2*2*2*2*2*2*2 possible combinations. Otherwise known as a maximum value of 32,768. We normally limit it to 32000 for an easier life.
So what happens is that some calculation results in a value greater than 32768 then tries to store it into a variable that can't hold it. Instant overflow and the program gives up in disgust.
By hovering the mouse, you can often find the exact variable or calculation that is causing the problem.
You need to report the line of code with as much information about the actual variables as possible. It also helps a lot to report the name of the subroutine in which the code is located. It can be an extremely daunting task just trying to find a specific line of code in the program without a little more info to go on.
In the case of a relatively small routine, just copy the whole routine and put it inside "code" tags in your message. Then describe the problem.
Hopefully I can look into some of this stuff later today.