You can do it with a table-level validation rule ...
UCase$([TestOne])<>UCase$([TestTwo])
(Where "TestOne" and "TestTwo" are the names of the two fields.)
In case you're not familiar with table-level validation rules, open the
table in design view, choose Properties from the View menu, make sure you
define the rule in the Table Properties dialog box, not in the properties
for individual fields - those field-level validation rules can not refer to
other fields in the table.
--
Brendan Reynolds (MVP)
http://brenreyn.blogspot.com
The spammers and script-kiddies have succeeded in making it impossible for
me to use a real e-mail address in public newsgroups. E-mail replies to
this post will be deleted without being read. Any e-mail claiming to be
from brenreyn at indigo dot ie that is not digitally signed by me with a
GlobalSign digital certificate is a forgery and should be deleted without
being read. Follow-up questions should in general be posted to the
newsgroup, but if you have a good reason to send me e-mail, you'll find
a useable e-mail address at the URL above.
Luke said:
I am trying to use a text field as the primary key in a table. The
problem is that the text values I'm importing contain 'duplicate' entries IF
text case is not considered (such as '5b' and '5B'). Access won't let me
use this column as the primary key because it sees that as a duplicate- how
can I get it to take case into account when determining duplicate records?
I've thought of using a seperate AutoNumber column as the primary key, but
I do want to enforce no duplication in the text column with case taken into
account. Anyone know how to do it?
