Thank you for your help... I'll try the trigger first.
I also thought about using an XML file, and have my application check to see
when it was created/updated.

Regards,
-Arbon


----- Original Message -----
From: "Breidenbach, Beth" <Beth.Breidenbach@g...>
To: "sql language" <sql_language@p...>
Sent: Thursday, March 29, 2001 2:20 AM
Subject: [sql_language] RE: Help with a SQL Constraint Statement


> Arbon,
>
> I believe you're going to be limited to using triggers for this, unless
> someone has a cool workaround.  Within a trigger you can check the count
and
> roll back the transaction.  Unfortunately, it's possible to bypass
triggers
> under certain conditions (like bulk copy).
>
> Beth
>
> -----Original Message-----
> From: Arbon Reimer [mailto:arbon_reimer@h...]
> Sent: Thursday, March 29, 2001 1:17 PM
> To: sql language
> Subject: [sql_language] Help with a SQL Constraint Statement
>
>
> Greetings!
>
> I wish to write a constraint statement that will allow only one record in
a
> table at one time... has anyone done this?  I've tried using a COUNT(*)
and
> SQL rejects that, and using a constraint
> @@ROWCOUNT = 1 doesn't seem to work either... any suggestions?
>
> Thanks very much
> Arbon Reimer
>
$subst('Email.Unsub')
>
>