On Jan 27, 6:30 pm, Marshall wrote:
There's another approach to enforcing constraints: just tell your
users not to do that. In the hierarchy of what works, it comes
below checks in client code, but above manually inserting
garbage at design-time. It also has the advantage of being
even lower performance overhead for the software.

Funny but I've actually seen this in the Access groups as an answer to
the alluded to question, "How do you prevent data corruption to your
'Access' data by users connecting via Excel?" (a common enough
scenario) i.e. put it in the staff handbook and make doing so a
disciplinary matter. Yes, I know: door...horse...bolted.

Jamie.

--