Multiple related tables for client contact information

[HLCruz via AccessMonster.com]

I was hired to clean up and reorganize a database that I did not create. We
have several issues, one of which is duplicated client contact data. Clean
up is difficult because the database was created with a central tFolder table
which contains the name and DOB but the address, phone number, email, etc.
were all created in separate, related tables. I'm first looking for any
opinions out there on the benefit to having all of this contact information
separated out into different tables. I just don't see it, and the separate
data has greatly hindered my ability to clean up the duplicates. Secondly,
any suggestions or experience in handling this would be appreciated.

 

[Jeff Boyce]

The primary reasons for needing separate tables is either that there is a
one (person) to many (address, phone, ...) relationship, or that there are
security concerns, and the tables are related one-to-one. What's the
situation at your end?

Have you tried creating queries that join person-to-address (and
person-to-phone, and ...) , and use those queries to help you resolve
duplication?

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[HLCruz via AccessMonster.com]

It appears that the database was designed for the one-to-many purpose.
However, this database was created for a non-profit organization and then
purchased by my organization. We may have an occaisonal occurance where
someone has more than one address, but not many. I suppose that it's not a
big deal once we get things cleaned up, but it sure is now!

I tried running some queries, but I really need to see ALL the data related
to a record in order to determine which record has the most complete data.
This inlcudes a total of 8 tables, when I ran a query to join all those
tables I couldn't open the results ... I figured the data set was too big.

I've spent the past several years working on FileMaker and am just getting
back into Acces so I'm very rusty. Do I need to run separate queries for
each related table?

My data is duplicated many times, there can be up to 5 or 6 records for one
person. Plus, thier information is spread out between all the related
records they have in the related tables. I'm beginning to wonder if I'm not
stuck having to manually clean up this data.

Thanks so much for your time

The primary reasons for needing separate tables is either that there is a
one (person) to many (address, phone, ...) relationship, or that there are
security concerns, and the tables are related one-to-one. What's the
situation at your end?

Have you tried creating queries that join person-to-address (and
person-to-phone, and ...) , and use those queries to help you resolve
duplication?

Regards

Jeff Boyce
Microsoft Office/Access MVP

I was hired to clean up and reorganize a database that I did not create.
We

[quoted text clipped - 11 lines]

Secondly,
any suggestions or experience in handling this would be appreciated.