# Error 11 â€“ Division by Zero in MS-Access Application

Asked By 1430 points N/A Posted on -

Hello,

I am posting here a problem regarding our company application, built in Microsoft Access.

When I was encoding on our survey about study habits of students, I was about to input-in time, an error message popped up with words which pointed to error 11 division zero.

Value: 0.579518616199493

Error Line: 80

Error: (11) Division by zero

This is my first time to encounter this error. I am wondering why other numeric fields accept data without an error, such as age, number of siblings, bedtime hours. But I remember, "the hours spend studying" input field has a new characteristic, it will round off to the nearest 15 minutes of the given hours.

SHARE
Answered By 0 points N/A #123387

## Error 11 â€“ Division by Zero in MS-Access Application

Â

Hello,

You found a mathematical error generated by the software. You did not provide enough information. There could be many problems. Divided by zero means, you are dividing some value by zero and its result is infinity and a computer cannot handle infinity value. So it generates an error and displays a message.

Somehow you gave a value which is equal to zero or the software is making it zero. You said you have a round function. Round function rounds a number and returns an integer (No decimal places like 2, 23, 46, etc.).

Somehow it is returning the zero value. To find out the main problem, you have to find the query used inside the program and need to understand how it is configured to use. It may be little critical.

Answered By 0 points N/A #123388

## Error 11 â€“ Division by Zero in MS-Access Application

Â

Hi Mikeallway,

Your error is generated by a division by zero, which is not allowed as infinity cannot be represented in computers.

You said about using a rounding function. If the result returned by this function is zero and is used in a division, then there is your problem.

Try to find the line of the program (80?) and look for that division. Programmers usually take precautions with such divisions and put a test before them, in order to avoid a null divisor. This is what you should do too.