Stop Number fields from automatically having a default value of 0
In Access 2013 and 2016, when I create a number field in a table, it automatically has a default value of 0. It is very annoying to have to clear this every time that I want to use it as a foreign key field, since the linked table doesn't have a record with a primary key of 0.
Can we down-vote? I rarely change it from zero and if I do, it's to another value, NOT nothing. It is too easy to batch edit object properties in vba or just copy a series of "what you really want" fields, when adding new fields to a table, to warrant the resources needed to make this change.
Tom Chambers commented
I agree with kb9zzo. Please add an Access or database level option to turn the default off for all number fields, including currency.
There is a big difference between knowing a value exists and stating that it is zero. The null value addresses this very nicely. Also, as kb9zzo mentioned, fields that are included in a unique index with "ignore nulls" turned on choke on the zero default.
I ask that you include the currency field with this option. I use the currency field to capture 64 bit hash code values -- the currency field is backwards compatible with earlier versions of Access, whereas the big integer / large number field is not. I index the currency field when I use it with hash codes.
If you have a lot of numeric fields in a table, it tedious to have to go through all of them and remove the default.
Thank you for considering this request.
Yes it works, but, as I mentioned, it is very annoying and I don't think that I have ever left the 0 in there, so I'm having to remove it all the time instead of putting in a value the few times when I might want it.
Microsoft Access Product Team commented
When you add a new number field, the Default Value property is set to 0, but you can change that (either in table design view in the lower property pane, or table datasheet view using the Default Value button in the Fields ribbon).
Is that not sufficient?
[Deleted User] commented
+1 here, but out of votes!!! If you want to set default value on fields, then you should give us the ability to define what the default values will be, but 0 would not be one in my books.