Difference making field Required and Specifying Is Not Null

[Gcook888]

I can't figure out what the difference is between making a field Required and
specifying Is Not Null as the Validation Rule other than the MS Access system
error msgs you get.

I am sure I am missing something but don't know what. Anybody know?

[Lucas]

>.
>

In my experience (and I've been playing around with these
methods for the past month), there are 3 ways to make a
field required.

1. In table design, under the Required property, set
Yes. This is the simplest way but the least effective.
I don't like this method because if you're on the phone,
jumping from field to field, if you tab over the Required
field it'll stop you and you may miss important info
elsewhere.

2. IsNotNul works about the same way (depending on where
you put the event procedure), but can be done on the
front end of a database (so that if you have two front
ends for two seperate users, one might have to put
something in, another might not).

3. Write VB code that refers to the Tag Property (which
can be set to Required). This way you can flag multiple
fields at once and run this test in the form's
BeforeUpdate procedure. This manner is my personal
preference.

Lucas