Also, it is blank when I first start out, but it populates with the zero's when I start to enter value inside a Field.

Just blank the Default Value. Also be sure to delete the Default Value from the table.

Thanks, I didn't notice the "0" in the Default Value in the Table.

Yeah. That's another area i go slightly against Ricks teaching (Particularly in the early phase). I do absolutely minimum with the tables other than set the field name and type. Things like validation rules and default values I always apply to form controls.

Easier to work with and can specify different rules for different forms (For example, your currency field. In this form, you don't want a default value so you remove the value. In another form you could set a default value.) Just my humble opinion

Thanks for the advice, I've worked with Acces since back in the '80's and just really getting back into it again. Access was quite different back when I graduated as a programmer in '89. A lot of newer and cooler stuff now with the breakout of all this technology.

That's awesome... Since Access 1.0 was released in 1992.  😁😁😁

I tend to avoid having nulls in numeric fields because that may cause math errors.  E.g. [Field1]+[Field2] returns null if either one is null.  Therefore, all numeric fields should have their "Required" property set to Yes (default is No).  That way, they can't be nullified at any level.  The user gets a warning message if he tries to.  If you want zero values to appear as blanks, set the "Format" property to "#" (see picture below).  The values will still be zeroes, and only the display format is in effect.  When the user clicks on it, the zero appears again to let the user know.  Leave the field, and it appears blank again.