I would suggest you put an after insert trigger which does the validation for you. If 2 fields are already null then it will just return an error and rollback else it will allow the insert to be committed.
regards, Anoop On 3/1/07, Kory Wheatley <[EMAIL PROTECTED]> wrote:
I have a database called accountcreation, and I want to setup a table called accountinfo. This table will require that two out of the three fields need to be "UNIQUE", I don't want duplications in these fields. One field is a integer value the other field is a character value. What is the best way to set this table up?
