Obligatory entry on form

[Rick Brandt]

"Lapchien" <cc8345@NOSPAMeclipse.co.uk> wrote in message
news:1059928544.242177@ananke.eclipse.net.uk...

> I'd like to make an entry obligatory in most of the fields on my form - not
> just TAB or 0, but an entry - this can be anything, as I've already setup my
> validation rules and texts. I've found though that a user can get around
> this just by tabbing through the form! Anyone know of a work-around?

Any reason you don't just set the fields as required in the table?

[Lapchien]

The ones I require are set as required - yes. But anyone can just 'tab'
through the form...




"Rick Brandt" <rvtjbrandt@sbcglobal.net> wrote in message
news:bgjfvi$piu2b$1@ID-98015.news.uni-berlin.de...

> "Lapchien" <cc8345@NOSPAMeclipse.co.uk> wrote in message
> news:1059928544.242177@ananke.eclipse.net.uk...

> > I'd like to make an entry obligatory in most of the fields on my form -

not

> > just TAB or 0, but an entry - this can be anything, as I've already

setup my

> > validation rules and texts. I've found though that a user can get

around

> > this just by tabbing through the form! Anyone know of a work-around?

>
> Any reason you don't just set the fields as required in the table?
>
>

[Rick Brandt]

"Lapchien" <cc8345@NOSPAMeclipse.co.uk> wrote in message
news:1059931893.660851@ananke.eclipse.net.uk...

> The ones I require are set as required - yes. But anyone can just 'tab'
> through the form...

But if they are "required" by the table they will not be able to save any
records where they didn't make an entry in those fields. They will get an error
message.

[Lapchien]

Is there any way to prevent them from leaving that particular field until an
entry has been made, that meets the required validation?


"Rick Brandt" <rvtjbrandt@sbcglobal.net> wrote in message
news:bgjh3a$pgjck$1@ID-98015.news.uni-berlin.de...

> "Lapchien" <cc8345@NOSPAMeclipse.co.uk> wrote in message
> news:1059931893.660851@ananke.eclipse.net.uk...

> > The ones I require are set as required - yes. But anyone can just 'tab'
> > through the form...

>
> But if they are "required" by the table they will not be able to save any
> records where they didn't make an entry in those fields. They will get an

error

> message.
>
>

[Lapchien]

Maybe - without sounding like a total shit the people doing the entering
aren't exactly brain surgeons...



"Rick Brandt" <rvtjbrandt@sbcglobal.net> wrote in message
news:bgjlm6$or4lv$1@ID-98015.news.uni-berlin.de...

> "Lapchien" <cc8345@NOSPAMeclipse.co.uk> wrote in message
> news:1059936169.424623@ananke.eclipse.net.uk...

> > Is there any way to prevent them from leaving that particular field

until an

> > entry has been made, that meets the required validation?

>
> I suppose you could test for an entry in the OnExit event of the control

and

> cancel the event if they didn't make an entry. Seems unnecessary though.
>
> After one or two instances where they get the Required Field errors for

leaving

> a control blank don't you think they'll pick up on the fact that they need

to

> make an entry?
>
>

[Sandra Daigle]

My preference is always to use the BeforeUpdate event of the form to test
for empty fields or to do cross field validation. It's not as annoying to
the user that way. You can use the BeforeUpdate event of each individual
control but it will only fire if a change has been made.

Putting the test code into the Exit event of the control is extremely
annoying because it will fire even when the user is trying to click a
command button or do something unrelated to saving the record.

--
Sandra Daigle
[Microsoft Access MVP]
For the benefit of others please post all replies to this newsgroup.

Rick Brandt wrote:

> "Lapchien" <cc8345@NOSPAMeclipse.co.uk> wrote in message
> news:1059936169.424623@ananke.eclipse.net.uk...

>> Is there any way to prevent them from leaving that particular field
>> until an entry has been made, that meets the required validation?

>
> I suppose you could test for an entry in the OnExit event of the control
> and cancel the event if they didn't make an entry. Seems unnecessary
> though.
>
> After one or two instances where they get the Required Field errors for
> leaving a control blank don't you think they'll pick up on the fact that
> they need to make an entry?