Input mask question

For some reason I just cannot get my head wrapped around the concept of input masks in Access database design. Can someone pls explain this concept, preferably with an example? TIA...
--
CMB from Omaha

an input mask is a way to help validate and modify the format of an entry.
For example, I have a field where a contract is entered. It is 7-digits
long. The first four digits are always characters (a-z) and the last three
are always number. I want all characters to be capital letters.

I can enter an input mask like...

LLLL000

The "" forces all characters to capitol case, regardless of whether they
are typed in caps or lower-case.

The "LLLL" means that a four letters must be entered.

The "000" means that three numbers must be entered.


Obviously your formatting would depend on your use. This is just one
example.

Hope that helps.

Rick B



"CMB from Omaha" wrote in message
...
For some reason I just cannot get my head wrapped around the concept of
input masks in Access database design. Can someone pls explain this
concept, preferably with an example? TIA...
--
CMB from Omaha

Thank you! Your example made a lot more sense than using a date, which is what I had been trying to do. (The display format was set differently than the input mask).

Just out of curiosity, do you happen to know an easy way to provide a more user-friendly error message when the data entry person "violates" the input mask? If my non-techy coworkers see an error message full of pound signs and angle brackets, they'll freak.
--
CMB from Omaha


"Rick B" wrote:

an input mask is a way to help validate and modify the format of an entry.
For example, I have a field where a contract is entered. It is 7-digits
long. The first four digits are always characters (a-z) and the last three
are always number. I want all characters to be capital letters.

I can enter an input mask like...

LLLL000

The "" forces all characters to capitol case, regardless of whether they
are typed in caps or lower-case.

The "LLLL" means that a four letters must be entered.

The "000" means that three numbers must be entered.


Obviously your formatting would depend on your use. This is just one
example.

Hope that helps.

Rick B



"CMB from Omaha" wrote in message
...
For some reason I just cannot get my head wrapped around the concept of
input masks in Access database design. Can someone pls explain this
concept, preferably with an example? TIA...
--
CMB from Omaha

There are ways to capture and change the error messages. If you can't find
the answer (do some searches) then post a new message in the Fomrs or
FomrsCoding newsgroups.

Rick


"CMB from Omaha" wrote in message
...
Thank you! Your example made a lot more sense than using a date, which is
what I had been trying to do. (The display format was set differently than
the input mask).

Just out of curiosity, do you happen to know an easy way to provide a more
user-friendly error message when the data entry person "violates" the input
mask? If my non-techy coworkers see an error message full of pound signs
and angle brackets, they'll freak.
--
CMB from Omaha


"Rick B" wrote:

an input mask is a way to help validate and modify the format of an entry.
For example, I have a field where a contract is entered. It is 7-digits
long. The first four digits are always characters (a-z) and the last
three
are always number. I want all characters to be capital letters.

I can enter an input mask like...

LLLL000

The "" forces all characters to capitol case, regardless of whether they
are typed in caps or lower-case.

The "LLLL" means that a four letters must be entered.

The "000" means that three numbers must be entered.


Obviously your formatting would depend on your use. This is just one
example.

Hope that helps.

Rick B



"CMB from Omaha" wrote in message
...
For some reason I just cannot get my head wrapped around the concept of
input masks in Access database design. Can someone pls explain this
concept, preferably with an example? TIA...
--
CMB from Omaha

Hi CMB,

IMHO they're not worth bothering with. Usually you get a far better user
experience by leaving the data entry flexible and using the Format
property or function to display it in the required way.

For very many domains (e.g. postal codes and telephone numbers) input
masks are a snare and a delusion: you get them working correctly for
your locality, and then one day you have to enter a contact in Mexico or
Belgium and you can't.



On Thu, 15 Jul 2004 09:26:02 -0700, "CMB from Omaha"
wrote:

For some reason I just cannot get my head wrapped around the concept of input masks in Access database design. Can someone pls explain this concept, preferably with an example? TIA...

--
John Nurick [Microsoft Access MVP]

Please respond in the newgroup and not by email.

"=?Utf-8?B?Q01CIGZyb20gT21haGE=?="
wrote in
:

For some reason I just cannot get my head wrapped around the concept
of input masks in Access database design.

I am with John N on this: they are an annoying nuisance that do nothing but
get in the way of the user. Strictly speaking, they are not part of the
database design anyway, but part of the GUI.

- they don't protect your data -- if you make a form and don't put the IMs
(or remove them from) the text boxes, then they won't appear anyway.

- they don't protect your data -- you can change data in fields using
queries, VBA, Excel (even CorelDraw!) which will completely bypass the IMs

- they don't protect your data -- just imposing limits on keystrokes does
not mean that 09/95/2003 is a valid date!

- ValidationRules, Referential Integrity, Unique Indexes _are_ part of the
database design and _do_ protect your data!

All the best


Tim F