Can I turn off 0 divide error, for denominator = 0
 

I have a macro with many divisions, for many
of the divisions both the numerator and denominator are zero.
It's the no data case, so it's 0/0 for that condition
(or else it's a fraction).
Office 2007, integer dimensioned values.
If denominator = 0 then denominator = 1
will get round it since it's then 0/1 and still equates
to 0.
But doing this comparison a million or so
times is clearly time consuming and inefficient.
With the current database, and growing, it's approx
5M divide by 0 tests.
Any suggestions?

Can I turn off 0 divide error, for denominator = 0
 

set the default value of all denominators to one rather than zero
--
Gary''s Student - gsnu200762

Can I turn off 0 divide error, for denominator = 0
 

Any time you divide you have to either check the denominator or trap the
error, welcome to the world of programming...

" wrote:

I have a macro with many divisions, for many
of the divisions both the numerator and denominator are zero.
It's the no data case, so it's 0/0 for that condition
(or else it's a fraction).
Office 2007, integer dimensioned values.
If denominator = 0 then denominator = 1
will get round it since it's then 0/1 and still equates
to 0.
But doing this comparison a million or so
times is clearly time consuming and inefficient.
With the current database, and growing, it's approx
5M divide by 0 tests.
Any suggestions?

Can I turn off 0 divide error, for denominator = 0
 

But, if I tested this right, 5M checks take less than half a second.... So why bother?

--
Kind regards,

Niek Otten
Microsoft MVP - Excel

"dlw" wrote in message ...
| Any time you divide you have to either check the denominator or trap the
| error, welcome to the world of programming...
|
| " wrote:
|
| I have a macro with many divisions, for many
| of the divisions both the numerator and denominator are zero.
| It's the no data case, so it's 0/0 for that condition
| (or else it's a fraction).
| Office 2007, integer dimensioned values.
| If denominator = 0 then denominator = 1
| will get round it since it's then 0/1 and still equates
| to 0.
| But doing this comparison a million or so
| times is clearly time consuming and inefficient.
| With the current database, and growing, it's approx
| 5M divide by 0 tests.
| Any suggestions?
|