Input Mask - 'Evil' and 'Not Useful'

Guys

I have researched the use of input masks for a problem I'm having (for which
I've posted separately), but I am interested in learning why some experts
have described input masks as 'evil' and 'not useful'. Some experts on the
forum have said input masks fail to provide flexibility. Are input masks ok
for simple things like, say, file numbers that have a particular format? (eg:
LH/09/01) I can understand the need for flexibility in more complicated
things. Are there better ways of forcing users to enter the proper, perhaps
unique, format? Grateful for some general advice on the issue of input masks.

Chris

I think part of the issue is people use input masks to push multiple data
values into a single field.

I generally expect users to be intelligent enough to enter values correctly.
I will often use the After Update event of a control to either correct the
value or pop up a PEBKAC (Problem Exists Between Keyboard And Chair) error
message and have the user try again.
--
Duane Hookom
Microsoft Access MVP


"Chris Lines" wrote:

Guys

I have researched the use of input masks for a problem I'm having (for which
I've posted separately), but I am interested in learning why some experts
have described input masks as 'evil' and 'not useful'. Some experts on the
forum have said input masks fail to provide flexibility. Are input masks ok
for simple things like, say, file numbers that have a particular format? (eg:
LH/09/01) I can understand the need for flexibility in more complicated
things. Are there better ways of forcing users to enter the proper, perhaps
unique, format? Grateful for some general advice on the issue of input masks.

Chris

My favorite two examples are using input masks on Zipcodes and Telephone
numbers. Looks like a good idea at first until you get to add a record for
someone from a different country! Try to put "OX9 6FA" into a USA zipcode
input mask or 0896 233999 into a USA/Canada phone number input mask.

If you are using input masks, you need to be very, very sure that it covers
all the bases. Like Duane, I tend to trust the users to input the right thing.

Now validation rules are quite another thing. I will check for things like
people inputting dates for the wrong century and such.
--
Jerry Whittle, Microsoft Access MVP
Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.

"Chris Lines" wrote:

Guys

I have researched the use of input masks for a problem I'm having (for which
I've posted separately), but I am interested in learning why some experts
have described input masks as 'evil' and 'not useful'. Some experts on the
forum have said input masks fail to provide flexibility. Are input masks ok
for simple things like, say, file numbers that have a particular format? (eg:
LH/09/01) I can understand the need for flexibility in more complicated
things. Are there better ways of forcing users to enter the proper, perhaps
unique, format? Grateful for some general advice on the issue of input masks.

Chris

Chris

My take:

Input masks require users to get it right or else. (... or at least what
the developer thought was 'right')

Validation rules (post or during data entry) allow users to do what they
know.

When you use a tool, do you want it to tell you how to use it, or do you
want it to help you to use it?

Regards

Jeff Boyce
Microsoft Office/Access MVP

"Chris Lines" wrote in message
...
Guys

I have researched the use of input masks for a problem I'm having (for
which
I've posted separately), but I am interested in learning why some experts
have described input masks as 'evil' and 'not useful'. Some experts on the
forum have said input masks fail to provide flexibility. Are input masks
ok
for simple things like, say, file numbers that have a particular format?
(eg:
LH/09/01) I can understand the need for flexibility in more complicated
things. Are there better ways of forcing users to enter the proper,
perhaps
unique, format? Grateful for some general advice on the issue of input
masks.

Chris

Duane

Thank you for your thoughts. I appreicate it.

Chris

"Duane Hookom" wrote:

I think part of the issue is people use input masks to push multiple data
values into a single field.

I generally expect users to be intelligent enough to enter values correctly.
I will often use the After Update event of a control to either correct the
value or pop up a PEBKAC (Problem Exists Between Keyboard And Chair) error
message and have the user try again.
--
Duane Hookom
Microsoft Access MVP


"Chris Lines" wrote:

Guys

I have researched the use of input masks for a problem I'm having (for which
I've posted separately), but I am interested in learning why some experts
have described input masks as 'evil' and 'not useful'. Some experts on the
forum have said input masks fail to provide flexibility. Are input masks ok
for simple things like, say, file numbers that have a particular format? (eg:
LH/09/01) I can understand the need for flexibility in more complicated
things. Are there better ways of forcing users to enter the proper, perhaps
unique, format? Grateful for some general advice on the issue of input masks.

Chris

Jerry

Thank you. I'll give more thought now to using validations rather than
masks. Although nowhere near the experience level of an MVP, I must confess
to some frustration with several users of the work database I have created.
Data quality has been poor in the past. Mind you, I would accept the users'
criticism that the database needed improvements. In any case, I shall embark
on some experimenting with validation rules. Thanks again, Jerry, for your
comments.

Chris

"Jerry Whittle" wrote:

My favorite two examples are using input masks on Zipcodes and Telephone
numbers. Looks like a good idea at first until you get to add a record for
someone from a different country! Try to put "OX9 6FA" into a USA zipcode
input mask or 0896 233999 into a USA/Canada phone number input mask.

If you are using input masks, you need to be very, very sure that it covers
all the bases. Like Duane, I tend to trust the users to input the right thing.

Now validation rules are quite another thing. I will check for things like
people inputting dates for the wrong century and such.
--
Jerry Whittle, Microsoft Access MVP
Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.

"Chris Lines" wrote:

Guys

I have researched the use of input masks for a problem I'm having (for which
I've posted separately), but I am interested in learning why some experts
have described input masks as 'evil' and 'not useful'. Some experts on the
forum have said input masks fail to provide flexibility. Are input masks ok
for simple things like, say, file numbers that have a particular format? (eg:
LH/09/01) I can understand the need for flexibility in more complicated
things. Are there better ways of forcing users to enter the proper, perhaps
unique, format? Grateful for some general advice on the issue of input masks.

Chris

Jeff

Thank you very much for your response. I will now give more thought to the
use of validation rules rather than relying solely on masks. Thanks again,
Jeff.

Chris

"Jeff Boyce" wrote:

Chris

My take:

Input masks require users to get it right or else. (... or at least what
the developer thought was 'right')

Validation rules (post or during data entry) allow users to do what they
know.

When you use a tool, do you want it to tell you how to use it, or do you
want it to help you to use it?

Regards

Jeff Boyce
Microsoft Office/Access MVP

"Chris Lines" wrote in message
...
Guys

I have researched the use of input masks for a problem I'm having (for
which
I've posted separately), but I am interested in learning why some experts
have described input masks as 'evil' and 'not useful'. Some experts on the
forum have said input masks fail to provide flexibility. Are input masks
ok
for simple things like, say, file numbers that have a particular format?
(eg:
LH/09/01) I can understand the need for flexibility in more complicated
things. Are there better ways of forcing users to enter the proper,
perhaps
unique, format? Grateful for some general advice on the issue of input
masks.

Chris

Hi Chris,

I agree with the other posters. I would add that often masks are often
a pain in the neck for those doing serious data entry. I find myself
detesting them when trying to enter data because they often require extra
work (keystrokes and/or mousings) to enter something that should be pretty
straight forward.

My $0.02 worth.

Clifford Bass

"Chris Lines" wrote:

Guys

I have researched the use of input masks for a problem I'm having (for which
I've posted separately), but I am interested in learning why some experts
have described input masks as 'evil' and 'not useful'. Some experts on the
forum have said input masks fail to provide flexibility. Are input masks ok
for simple things like, say, file numbers that have a particular format? (eg:
LH/09/01) I can understand the need for flexibility in more complicated
things. Are there better ways of forcing users to enter the proper, perhaps
unique, format? Grateful for some general advice on the issue of input masks.

Chris

Clifford

Thank you. The masks I have used to date do indeed require extra key
strokes, so I see your point. But my inputers are regularly getting the input
format wrong (in my case it's a file-number format), which in turn means my
searches don't always give me the results I should get. I'm going to fiddle
with some validation rules and see how that goes. Thanks again, Clifford, for
your comments.

Chris

"Clifford Bass" wrote:

Hi Chris,

I agree with the other posters. I would add that often masks are often
a pain in the neck for those doing serious data entry. I find myself
detesting them when trying to enter data because they often require extra
work (keystrokes and/or mousings) to enter something that should be pretty
straight forward.

My $0.02 worth.

Clifford Bass

"Chris Lines" wrote:

Guys

I have researched the use of input masks for a problem I'm having (for which
I've posted separately), but I am interested in learning why some experts
have described input masks as 'evil' and 'not useful'. Some experts on the
forum have said input masks fail to provide flexibility. Are input masks ok
for simple things like, say, file numbers that have a particular format? (eg:
LH/09/01) I can understand the need for flexibility in more complicated
things. Are there better ways of forcing users to enter the proper, perhaps
unique, format? Grateful for some general advice on the issue of input masks.

Chris

Hi Chris,

You are welcome!.

You may want to consider splitting the entry of the information into
separate text boxes, even if you rejoin it behind the scenes for storage in
the table.

Clifford Bass

"Chris Lines" wrote:

Clifford

Thank you. The masks I have used to date do indeed require extra key
strokes, so I see your point. But my inputers are regularly getting the input
format wrong (in my case it's a file-number format), which in turn means my
searches don't always give me the results I should get. I'm going to fiddle
with some validation rules and see how that goes. Thanks again, Clifford, for
your comments.

Chris