Roy,

Actually, I just fixed the original problem.  I don't know why, but for some
reason I was thinking that the IS NOT NULL syntax would get mixed up with
the NOT NULL syntax, but since there is no leading IS keyword, then the
parser can distinguish between the two just fine.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim

>Perhaps. The problem is that when the table is then looked at again, the
>Required property will not be true for the column, but rather there will be
>a constraint. So, I'd rather leave it to the developer to make the changes
>in terms of adding a constraint, etc., and instead just issue an exception
>if the developer tries to add a Required/Generated column using the Alter
>Table functionality.

Fair enough

Roy Lambert

Tim

IS NOT NULL <> NOT NULL

But shouldn't that end up as unknown

Roy Lambert

Roy,

<< IS NOT NULL <> NOT NULL

But shouldn't that end up as unknown >>

No, because it is known that the two unknown checks are....aw forget it.

--
Tim Young
Elevate Software
www.elevatesoft.com