Re: Duplicate Values Question

Users should NEVER be allowed to work directly with tables or queries.
Create a form in data*** view if that is most comfortable for them. You
can then put edit code in the various events to validate data.

Jet doesn't support triggers which would solve your problem but it is really
a non-problem since if the back end were SQL Server, you wouldn't even
consider letting the users at the tables directly.

<runnik@xxxxxxxxx> wrote in message
news:96895ec4-0b7d-4859-8d3a-173eeb4ad8e1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I have a table containing, among others, a field titled
numSerialNumber ("SN") and a field titled strBoardNumber ("BN"). The
SN field is the primary key, and the BN field is required.
Additionally, the BN field must contain a unique value, unless the SN
gets voided. In that case, the BN field can contain "VOID".

Is there any way to allow this, and to have this check at the table
level? Users will sometimes access the table directly to quickly find
a record that needs to be corrected, and I don't want them to
accidentally change the BN field to a duplicate value.

Or, do I need to just implement something at the form level, and tell
users to view the form in data*** view if they need to make
corrections?

Jason


.