Input mask not working for importing

When creating an input mask for a field when using it, it does exactly what
it is suppose to do.
However when importing data from another file (csv or excel) the values in
this field that are correct but in the wrong case get rejected despite the
input mask which (when input occurs in datasheet view) changes the data to
correct case.
For instanceL;; makes capitals out of any input letter
However when importing 10 records with 5 lowercase and 5 uppercase values in
this field the 5 lowercase records are rejected.
Isn't this suppose to be the work of the input mask?

Anybody any idea?
Cheers dion

On Tue, 30 Aug 2005 11:37:01 -0700, "Dion van Overdijk"
wrote:

When creating an input mask for a field when using it, it does exactly what
it is suppose to do.
However when importing data from another file (csv or excel) the values in
this field that are correct but in the wrong case get rejected despite the
input mask which (when input occurs in datasheet view) changes the data to
correct case.
For instanceL;; makes capitals out of any input letter

No. It doesn't. It DISPLAYS the data as capitals; the data is stored
as typed.

However when importing 10 records with 5 lowercase and 5 uppercase values in
this field the 5 lowercase records are rejected.
Isn't this suppose to be the work of the input mask?

No, it's NOT the function of an input mask.

An input mask does two things: it constrains what the user is allowed
to type when manually entering data into the field; and it affects the
way data in a field is displayed, in a limited manner (not as powerful
as the Format property).

Access tables are inherently non-case sensitive, and they cannot be
made case sensitive. It sounds like you have a unique Index (such as a
Primary Key) on a field, and you're trying to import XYZZY and xyzzy
and Xyzzy as three different records. This will indeed fail; to
Access, these are three duplicate values, and will generate an error
if duplicates are not allowed in this field. The Input Mask has
absolutely NO relation to this; you could use a different mask, or no
mask at all, and the import would work exactly the same.

John W. Vinson[MVP]