It's a good article and one that is even more appropriate if the OP is
using ADO.

I was going to link to this:

http://office.microsoft.com/en-us/assistance/HP010322071033.aspx

...however, it is very confused, IMO.

For example, can anyone explain this to me?

"You can use NOT NULL on a single field or within a named CONSTRAINT
clause that applies to either a single field or to a multiple-field
named CONSTRAINT"

I am aware this is legal syntax:

CREATE TABLE Test5 (
data_col INTEGER
CONSTRAINT data_col__not_null NOT NULL);

Legal but seems to provide no functionality: I can give the NOT NULL
constraint a name but the name does not seem to be retained e.g. in the
ADO's TABLE_CONSTRAINTS schema rowset
(http://msdn.microsoft.com/library/default.asp?url=/library/en-us/oledb/htm/oledb
table_constraints_rowset.asp).

However, I can't see how to use this in an ALTER TABLE statement. If
this is the case, why is it mentioned here?

It remind me of this still-unsolved mystery in the same help:

http://office.microsoft.com/en-us/assistance/HP010322201033.aspx

CREATE [TEMPORARY] TABLE

"When a TEMPORARY table is created it is visible only within the
session in which it was created. It is automatically deleted when the
session is terminated. Temporary tables can be accessed by more than
one user."

Jamie.

--