the default value of zero in fields with a Number data type

By default, Access gives a Default Value of 0 to fields with a Number data
type. I have been removing this value of zero from the Default Value
property of my Number fields, because I've considered it a minor annoyance
of no value.

I'm wondering if there's any disadvantage to doing this. That is, is there
any benefit to retaining a default value of 0 in Number fields?

Thanks in advance,

Paul

Paul

As a statistician in a former life, my bias is that the "0" default is a
serious mistake. "0" is a value which implies something's been measured and
found to be ... "0". If I see a list of numbers, with "0"s, I assume those
are meaningful values.

I kill the "0" defaults too.

--
Good luck

Jeff Boyce
Access MVP

On Thu, 17 Jun 2004 11:15:46 -0700, "Paul James"
wrote:

That is, is there
any benefit to retaining a default value of 0 in Number fields?

Only occasionally - when in the real world the number stored in this
field represents a value which can be assumed to be zero unless
otherwise specified. For instance, a PenaltyFee field could well be
zero, assuming that ordinarily there would be no such fee charged.
NULL is a mite less convenient in this case since you'ld need to use
NZ() to do math with the value.

The zero default on foreign key fields is a MAJOR pain in the neck of
course!

John W. Vinson[MVP]
Come for live chats every Tuesday and Thursday
http://go.compuserve.com/msdevapps?loc=us&access=public

Thanks, gentlemen, for your comments.

I think I'll keep removing those zeroes from the default value property of
my Number fields.