T
Tom Ellison
Dear friends:
I've just had an experience in Access that disturbs me.
A table is open in Design View, with the Indexes dialog showing. I select
the primary key and change the Primary attribute to No.
I get:
You can't change the primary key.
This table is the primary table in ome or more relationships.
If you want to change or remove the primary key, first delete the
relationship in the relationship window.
This makes no sense. A relationship can be on any unique index (on the
"one" side). It doesn't have to be on the Primary Key. Making an index not
primary has nothing to do with this!
It would be proper to prevent me removing the index, or making it not "No
Duplicates". But surely it does not HAVE to be the primary key.
Is my thinking correct?
Why would MS do this?
Tom Ellison
I've just had an experience in Access that disturbs me.
A table is open in Design View, with the Indexes dialog showing. I select
the primary key and change the Primary attribute to No.
I get:
You can't change the primary key.
This table is the primary table in ome or more relationships.
If you want to change or remove the primary key, first delete the
relationship in the relationship window.
This makes no sense. A relationship can be on any unique index (on the
"one" side). It doesn't have to be on the Primary Key. Making an index not
primary has nothing to do with this!
It would be proper to prevent me removing the index, or making it not "No
Duplicates". But surely it does not HAVE to be the primary key.
Is my thinking correct?
Why would MS do this?
Tom Ellison