I've been wrestling with a design dilemma for a few days and I'd welcome some advice.
I know that it is technically possible in Access to set up a relationship in which a foreign key in one table references a non-primary, but unique, indexed field in another table.
I have a situation where it seems I may need to create tables using such a setup... but I can't help thinking that it seems a bad idea.
Can anyone offer any advice on whether using non-primary (but obviously unique) keys in relationships is generally bad practice or if it is OK? Thanks.
I know that it is technically possible in Access to set up a relationship in which a foreign key in one table references a non-primary, but unique, indexed field in another table.
I have a situation where it seems I may need to create tables using such a setup... but I can't help thinking that it seems a bad idea.
Can anyone offer any advice on whether using non-primary (but obviously unique) keys in relationships is generally bad practice or if it is OK? Thanks.