Input Mask Question

I just don't understand something findemental about input masks. Please
enlighten me.

I can set an input mask on table fields, and I can also set it on Form
fileds. *I WOULD THINK* that if I put the inopaut mask in the form design,
that it would always cary over if that field is used in a form.
I know I could set the mask up in the form . . .but I have to do it
everywhere that field is used.

Am I missing something??

"Mixer1" wrote in message
...
I just don't understand something findemental about input masks. Please
enlighten me.

I can set an input mask on table fields, and I can also set it on Form
fileds. *I WOULD THINK* that if I put the inopaut mask in the form design,
that it would always cary over if that field is used in a form.
I know I could set the mask up in the form . . .but I have to do it
everywhere that field is used.

Am I missing something??

If you set certain properties at the table level and then use a wizard to build
a form or report based on that table some of those properties will be carried
over, but it is the wizard (generally) that makes that happen. Properties (for
the most part) are not inherited. Certainly if you make such changes at the
table level forms and reports that already exist will not pick those properties
up.

p.s. Input Masks are evil.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

Duh!

OK OK I guess I added the masks after the form was created with the wizard!!!

So, if the property is there in the table before a FORM IS CREATED, it
should carry over?

Long day . . . .

"Rick Brandt" wrote:


"Mixer1" wrote in message
...
I just don't understand something findemental about input masks. Please
enlighten me.

I can set an input mask on table fields, and I can also set it on Form
fileds. *I WOULD THINK* that if I put the inopaut mask in the form design,
that it would always cary over if that field is used in a form.
I know I could set the mask up in the form . . .but I have to do it
everywhere that field is used.

Am I missing something??

If you set certain properties at the table level and then use a wizard to build
a form or report based on that table some of those properties will be carried
over, but it is the wizard (generally) that makes that happen. Properties (for
the most part) are not inherited. Certainly if you make such changes at the
table level forms and reports that already exist will not pick those properties
up.

p.s. Input Masks are evil.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

"Mixer1" wrote in message
...
Duh!

OK OK I guess I added the masks after the form was created with the wizard!!!

So, if the property is there in the table before a FORM IS CREATED, it
should carry over?

Long day . . . .

Given the variety of Access versions and wizards out there, "should" might be
too strong a choice of words. Suffice to say that it sometimes happens. When
it doesn't you need to add them yourself.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

Note, Rick's note "input masks are evil"

A few notes regarding input masks:

The do not have any effect on how the data are stored nor how they are
displayed. They are only intended to ensure the entry conforms to a specific
format.

They are more trouble than they are worth.
--
Dave Hargis, Microsoft Access MVP


"Mixer1" wrote:

Duh!

OK OK I guess I added the masks after the form was created with the wizard!!!

So, if the property is there in the table before a FORM IS CREATED, it
should carry over?

Long day . . . .

"Rick Brandt" wrote:


"Mixer1" wrote in message
...
I just don't understand something findemental about input masks. Please
enlighten me.

I can set an input mask on table fields, and I can also set it on Form
fileds. *I WOULD THINK* that if I put the inopaut mask in the form design,
that it would always cary over if that field is used in a form.
I know I could set the mask up in the form . . .but I have to do it
everywhere that field is used.

Am I missing something??

If you set certain properties at the table level and then use a wizard to build
a form or report based on that table some of those properties will be carried
over, but it is the wizard (generally) that makes that happen. Properties (for
the most part) are not inherited. Certainly if you make such changes at the
table level forms and reports that already exist will not pick those properties
up.

p.s. Input Masks are evil.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

So, if the property is there in the table before a FORM IS CREATED, it
should carry over?

slight modification to: So, if the property is there in the table before a
field is added to a form, it should carry over?

i.e., if you add a mask (or other property) to a field at the table level,
you *might* be able to delete the field from an existing form, add it again
and have the mask appear. Doesn't matter when the form was created, it
matters when the field was added to the form.

--
HTH,
George



"Mixer1" wrote in message
...
Duh!

OK OK I guess I added the masks after the form was created with the
wizard!!!

So, if the property is there in the table before a FORM IS CREATED, it
should carry over?

Long day . . . .

"Rick Brandt" wrote:


"Mixer1" wrote in message
...
I just don't understand something findemental about input masks. Please
enlighten me.

I can set an input mask on table fields, and I can also set it on Form
fileds. *I WOULD THINK* that if I put the inopaut mask in the form
design,
that it would always cary over if that field is used in a form.
I know I could set the mask up in the form . . .but I have to do it
everywhere that field is used.

Am I missing something??

If you set certain properties at the table level and then use a wizard to
build
a form or report based on that table some of those properties will be
carried
over, but it is the wizard (generally) that makes that happen.
Properties (for
the most part) are not inherited. Certainly if you make such changes at
the
table level forms and reports that already exist will not pick those
properties
up.

p.s. Input Masks are evil.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com