Problem with having too many nulls

[Lee Stafford via AccessMonster.com]

I have a report that will crash when a certain table doesn't have any data.
This is hard to explain, so please bear with me.
This is a monthly report that lists technicians, Jobs Completed, Jobs
inspected, % Jobs Inspected, Total Disconnects, Avg Disco Score. The problem
I am having is the Jobs Completed field. That field must be entered
separately from all the others. The only reason it is needed, is to
calculate the % Jobs Inspected. In the middle of the month, we don't really
need that figure, but would like the rest of the report. However, if we
don't enter in how many jobs were completed, the report will crash if there
are too many techincians. I am assuming because there are too many nulls.

Any ideas of how I can fix this?

Thanks,

Lee

 

[SusanV]

Set the default value of the field to 0 to avoid the null.

 

[Lee Stafford via AccessMonster.com]

Thank you for your suggestion. I found my problem to actually be something
really stupid and staring me in the face. The probllem wasn't the nulls in
this case, it was that one of the records did have a zero in this field.
Another field was being divided by this field. Can't divide by zero.
I will use your suggestion for future problems with nulls, though.

Thanks,
Lee

 

[SusanV]

Glad you found and corrected the problems!

Susan