By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,851 Members | 1,492 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,851 IT Pros & Developers. It's quick & easy.

Null VS. 0 as default value in number field

rsmccli
P: 52
Is there any benefit to having 0 instead of null as a default value for combobox/lookup fields? Just wondering because I find the default 0s annoying and am thinking about going through and deleting them all.

Thanks for your time,
rsmccli
Mar 11 '08 #1
Share this Question
Share on Google+
2 Replies


missinglinq
Expert 2.5K+
P: 3,532
Your post and your title don't match! I assume that you're referring to a numbers field, as your title states, as your reference in the post to combobox/lookup fields makes no sense. I find the zeros annoying and always delete them when creating a table. Unless you have Access set up to hilite a field on entering it (which is a dangerous practise as it can lead to accidental loss of data) you have to delete the zero before entering your data. And if you usually use the IsNull() function to do data validation it won't pick up that you've not entered any data because the control won't be Null, it'll have the zero in it!

Linq ;0)>
Mar 11 '08 #2

P: 15
I prefer to avoid nulls whenever possible. Operations (math, compares etc) with nulls require more work than if they are 0's.

It may be a little more work to restrict nulls initially, but I feel it pays off in the long run.

just my opinion.

http://www.db-pros.com
Mar 11 '08 #3

Post your reply

Sign in to post your reply or Sign up for a free account.