I have a database that is a typical contact database where my table design has a one to many relationship for companies and contacts. That is, one company has many contacts but one contact can only be in one company.
This has worked great for years and never had an issue. Now I'm looking at a contact that actually works at two companies. I could create the same contact in both companies, but this contact has the same phone number and email, etc... which could lead to errors when only one of the two entries is updated.
The best way would be to use tags or links, but I don't think Access is able to do that. At least not my version of Access 2003.
So what would be the best way to deal with type of situation without making a huge change to the table structure / design.
Thanks
This has worked great for years and never had an issue. Now I'm looking at a contact that actually works at two companies. I could create the same contact in both companies, but this contact has the same phone number and email, etc... which could lead to errors when only one of the two entries is updated.
The best way would be to use tags or links, but I don't think Access is able to do that. At least not my version of Access 2003.
So what would be the best way to deal with type of situation without making a huge change to the table structure / design.
Thanks