Forum Discussion
Default value not recognized
This is probably not the answer you want, but from what I can see in the screen shot and your description, the problem is actually an inappropriate table design for a relational database application.
Your table appears to have multiple columns--like a spreadsheet would--for things like "Passing" and "Body Awareness" and so on. These are all attributes of one kind of thing, not separate kinds of things.
As a general guess, I'd say that thing is "Safety Principles", of which "Bend at Knees", "Move Feet" and so on are different aspects, or attributes.
You have a set of additional fields, paired with these, which accept "Yes" or "No" or perhaps "1" or nothing.
This approach is, unfortunately, all too common among people new to relational database applications, but it creates hurdle after hurdle when it comes to data entry, as you have found.
The overall guideline is that tables should be "tall and skinny" not "short and wide". Multiple columns like yours create short, wide tables.
Rather than repeat a lot of these principles here, I'm going to suggest you study the series of articles in this blog which explain the design problem in more detail and also guide you through the necessary redesign to make this work.
Among other things, you'll learn that you do not have to seed the record with all those 0 values along with all the hassle that creates. Instead, you simply add one new record each time an employee passes one of the criteria for a specific safety principle on which they are being observed.