Robert wrote:

> Since the field (like others in the table) must not be NULL, the
> front-end software then updates all existing records to have a value of
> 0, and this update is successful (no errors are reported, and FlameRobin
> shows the field as being set to 0, not NULL).
>
> However, if I then try to update any other field, I get an error
> reported. DAO reports it as error 3197, but FlameRobin reports:
>
> The insert failed because a column definition includes validation
> constraints.
> Engine Code: 335544347
> Engine Message:
> validation error for column AlwaysMonitor, value "***null***".
>
> The problem is that AlwaysMonitor isn't NULL; it's 0.

I can confirm I have seen similar problems, but I have not reported
(yet) because I couldn't create a reproducible test case.

Is there some chance you could create a reproducible test case?

--
Milan Babuskov
http://www.flamerobin.org
http://www.guacosoft.com