Validation is not working on Combo

THis appears to be like a previous problem but I would
like to know if it can be solved without writing code.

Form control is Combo Box.
It is filling a number field into a table.
Source has 3 columns (LName, FirstName, ID) and bound
column is 3.
It is limited to list. There are no default values.
I want to validate that something was chosen.(anything-
that is, don't leave it blank)
When I try to put a validation rule of "is not null" I
expected to have it reject but it doesn't.
When I put in += 0" as the rule, it does not reject a non-
choice.

I can't get it to work on the Table level either!
I could only cause a reject if I said the Field in table
was required, but that message is too generic and will not
be understood by the User.
Help!

Ruth,

I also would expect a Validation Rule of Is Not Null to result in a
"rejection". I think you realise that such a rejection only happens at
the point you are trying to commit the record, not at the point where
you leave the combobox? And your statement about no default values
applies to the field definition in the table as well as the form control?

--
Steve Schapel, Microsoft Access MVP


Ruth wrote:
THis appears to be like a previous problem but I would
like to know if it can be solved without writing code.

Form control is Combo Box.
It is filling a number field into a table.
Source has 3 columns (LName, FirstName, ID) and bound
column is 3.
It is limited to list. There are no default values.
I want to validate that something was chosen.(anything-
that is, don't leave it blank)
When I try to put a validation rule of "is not null" I
expected to have it reject but it doesn't.
When I put in += 0" as the rule, it does not reject a non-
choice.

I can't get it to work on the Table level either!
I could only cause a reject if I said the Field in table
was required, but that message is too generic and will not
be understood by the User.
Help!

Thanks for your reply. the answers a

I also would expect a Validation Rule of Is Not Null to
result in a "rejection". I think you realise that such a
rejection only happens at the point you are trying to
commit the record, not at the point where you leave the
combobox?
Yes.

And your statement about no default values applies to the
field definition in the table as well as the form control?

Yes! So is this a bug?
Ruth
--
Steve Schapel, Microsoft Access MVP


Ruth wrote:
THis appears to be like a previous problem but I would
like to know if it can be solved without writing code.

Form control is Combo Box.
It is filling a number field into a table.
Source has 3 columns (LName, FirstName, ID) and bound
column is 3.
It is limited to list. There are no default values.
I want to validate that something was chosen.(anything-
that is, don't leave it blank)
When I try to put a validation rule of "is not null" I
expected to have it reject but it doesn't.
When I put in += 0" as the rule, it does not reject a
non-
choice.

I can't get it to work on the Table level either!
I could only cause a reject if I said the Field in
table
was required, but that message is too generic and will
not
be understood by the User.
Help!
.

Ruth,

No, it's not a bug. I am sure there is a perfectly rational
explanation, which needs to be tracked down. What happens if you try to
enter a record directly into the table, with nothing entered into this
field? No validation message? And the record is saved, with the field
blank? If so, do you get the same thing if you make a new table, and
try the same in there?

--
Steve Schapel, Microsoft Access MVP


wrote:
Thanks for your reply. the answers a


I also would expect a Validation Rule of Is Not Null to

result in a "rejection". I think you realise that such a
rejection only happens at the point you are trying to
commit the record, not at the point where you leave the
combobox?
Yes.


And your statement about no default values applies to the

field definition in the table as well as the form control?

Yes! So is this a bug?
Ruth

--
Steve Schapel, Microsoft Access MVP