Poor DDL support in Microsoft access…
Posted on 2004-03-31
Poor DDL in Microsoft access…
Why can’t I use this DDL?
create table Currency
CurCode Text(3) not null,
constraint PK_CURRENCY primary key (CurCode)
The table name currency is not allowed within DDL and also the column name memo is not accepted. When I change those names into CCurrency and Memo into Comment, I can execute the DDL. When I enter into designer mode I can change those names back into Currency and Memo again. Why the difference between DDL and a real hand job?
Also cascade delete and update can not be defined within DDL?
Any work around?