Division by zero

vijayanderson

Hi Friends,

I got the following error when Invoice has been posted "Division by Zero " 0/0, when sale order is posted.

Regards,
vijay

mohana_cse06

at anytime.u shdn't get this error. [-X

David_Singleton

vijayanderson wrote:

Hi Friends,

I got the following error when Invoice has been posted "Division by Zero " 0/0, when sale order is posted.

Regards,
vijay

Interesting. Is this 3.56? I never knew that this version was even released in India.

Either way this looks like an error in the Invoice Report, probably some code to print the unit cost by dividing the Amount by Quantity.

Its going to be very hard to fix though, because you will find it very difficult to even find a developer with a license.

vijayanderson

No. its 4.0 (sp3) with all Hot fixes.

garak

then u are in the wrong forum.

Is there are some customized code?
Did you have checked the source with using the debugger?

kriki

[Topic moved from 'Navision DOS' forum to 'NAV/Navision' forum]

vijayanderson

yes i have run the debugger, it goes to code unit 6500.

ssingla

Is the database customized. Start the debugger and check where the error comes. I remember the error used to come when I started using upgraded 4.0 sp3 database, but now i do not remember the solution/cause. Some details might help to remember.

garak

vijayanderson wrote:

yes i have run the debugger, it goes to code unit 6500.

And where there? Is there some customized source or is it all "standard".
Copy the codesnippes and the functionname here for a better help.

Regards

DenSter

vijayanderson wrote:

yes i have run the debugger, it goes to code unit 6500.

So you have the debugger on, you have traced the error, you know where it is. What exactly is your question then :-k

garak

DenSter wrote:

What exactly is your question then :-k

Maybe how he can prevent the division by zero .....

DenSter

garak wrote:

Maybe .....

Exactly my point. There is no question, and everyone is guessing what the problem is.

Savatage

Just have to add the 0 catch to the code

if C=0
then a=0
else A := B / C

DenSter

or:

IF C = 0 THEN 
  C := 1;
A := B/C;

David_Singleton

or in light of how much infromation the OP has given so far:

A := RAND(1);

which save a lot of lines of code. \:D/

DenSter

Thanks David, you made me spray my water on my screen

garak

David , , now on my screen is also water

kine

Problem is that if you make some "Workaround" to not have this error, you can be in big troubles, becuase you haven't solved the core problem, just the effect. And it can lead e.g. to some costing problems in future (just example). In most cases, when you get this error, it means that the data are wrong. In cases, when you can assume, that the divider will be zero, there will be appropriate condition. If it is not there, you can assume that when the divider is 0, there is some problem because it cannot be zero from the logic.

Conclusion: just think about the meaning of the code, do not just blindly make "workaround" to prevent this error. There can be deeper problem in this. 8)

Sog

With Rand as a user defined function which has this code: http://xkcd.com/221/

DenSter

kine wrote:

Problem is that if you make some "Workaround" to not have this error, you can be in big troubles, becuase you haven't solved the core problem, just the effect.

=D> Finally some intelligence in this thread
It's true, rather than write code to blindly prevent the division by zero, it would be better to put in a different, more descriptive, error message. We're so bent on "division by zero should not happen", but forget the underlying problem.

If the process needs to divide by a quantity, and that quantity is 0, the original line is not correct, so the error message should still come up, but with a descriptive message (something like "there is nothing to divide" )

Savatage

kine wrote:

Problem is that if you make some "Workaround" to not have this error, you can be in big troubles, becuase you haven't solved the core problem, just the effect. And it can lead e.g. to some costing problems in future (just example). In most cases, when you get this error, it means that the data are wrong. In cases, when you can assume, that the divider will be zero, there will be appropriate condition. If it is not there, you can assume that when the divider is 0, there is some problem because it cannot be zero from the logic.

Conclusion: just thing about the meaning of the code, do not just blindly make "workaround" to prevent this error. There can be deeper problem in this. 8)

Perfect example is we were trying to show on a form the actual quantity on hand QOH / Item."Sales Unit Of Measure".
Once in a while we get the division error. So as stated above the deeper problem was that someone was not filling in the UOM fields. So the next step was making the UOM mandatory. Therefore solving the deeper underlying problem.