Force Filed Input?

[MBM]

Force Field Input?

In the table properties required is set to yes on all fields and additionally most fields have a validation rule or input mask and validation text. I have created a form but the validation rules/input mask only kick in when the user tries to save the record or move to another record. Is there a way to prevent the user moving between fields before data is entered? e.g. a forename can only be entered once the date is entered, a surname can only be entered if the forename has been entered etc, etc.

 

[vbaInet]

For that level of validation, it would have to be done in code I'm afraid. Or macros, if you're that inclined.

 

[MBM]

Re: Force Field Input?

Thanks for the quick reply. How would I use a macro to enable forced entry?

 

[vbaInet]

I don't really use macros, but it's something you can quickly google for a quick tutorial.

Bear in mind that having this level of constraints might aggravate your users. In my honest opinion, your current level of validation is just the ticket. This is how most commercial databases are built.

 

[MStef]

Look at "DemoForceFieldA2002.mdb" (attachment, zip).
Open Form1 and try. (Look at VBA).

 

[MBM]

I don't really use macros, but it's something you can quickly google for a quick tutorial.

Bear in mind that having this level of constraints might aggravate your users. In my honest opinion, your current level of validation is just the ticket. This is how most commercial databases are built.

The intention is to aggravate the users! We're moving from a paper order form to a computerised form because my colleagues are a bunch of slackers and continually omit details such as names, items ordered, telephone numbers etc, etc which doubles my workload.

 

[vbaInet]

The intention is to aggravate the users! We're moving from a paper order form to a computerised form because my colleagues are a bunch of slackers and continually omit details such as names, items ordered, telephone numbers etc, etc which doubles my workload.

Looks like MStef has something for you in his attachment.

 

[MBM]

Look at "DemoForceFieldA2002.mdb" (attachment, zip).
Open Form1 and try. (Look at VBA).

That has the same problem. I can press the Tab key or press the mouse in the next field (f3LName) to skip f3FName and the validation only kicks in once I try to skip f3LName. I need to make the form idiot proof

 

[vbaInet]

It would be difficult performing this level of validation if the form is bound (which I suspect it is).

If you want to achieve this then you can make your form unbound but you would need custom buttons and code to handle insert, update and delete actions.

 

[ghudson]

You should only need to perform the validation if the user tries to move off the current record or save the current record or close the form if all of your required fields are not completed. Slapping their hand if they jump to the wrong field before they completed a previous field is just cruel and a great way to make the users not want to use your database.

These should give you some pointers... best way to ensure saving changes and Form closes before Mandatory fields filled