Sub Sub and Circular

[Dan]

I want to make a database with Subjects of contact. Companies of contact.
And, Names of contact.

The "Names" fields (with phones and extention, email, etc.) are unique to
certain "Companies" fields (with addresses, faxes, etc.). Further the
"Companies" fields are unique to certain "Subject" fields (jobs offered by
company).

Up to now, I've put everything in one table. But the companies are becoming
redundant. Futher, the contacts at the companies are beginning to become
diverse (with their unique phones). I've been able to put the fields in
queries and edit them as needed. However, I'd like to relate the data from
two or three different tables and still be able to edit them. I havn't been
able to figure out how to edit and, indeed, add new data the adjacent tables
by using data in a look-up field.

Does anyone have any suggestions.

TIA,
Dan

 

[Smartin]

I want to make a database with Subjects of contact. Companies of contact.
And, Names of contact.

The "Names" fields (with phones and extention, email, etc.) are unique to
certain "Companies" fields (with addresses, faxes, etc.). Further the
"Companies" fields are unique to certain "Subject" fields (jobs offered by
company).

Up to now, I've put everything in one table. But the companies are becoming
redundant. Futher, the contacts at the companies are beginning to become
diverse (with their unique phones). I've been able to put the fields in
queries and edit them as needed. However, I'd like to relate the data from
two or three different tables and still be able to edit them. I havn't been
able to figure out how to edit and, indeed, add new data the adjacent tables
by using data in a look-up field.

Does anyone have any suggestions.

TIA,
Dan

Hi Dan, the quick suggestion (though more work for you (^: ) is to
Google on "database normalization". Understand the first, second, and
third "normal forms". You might try "entity modeling" too. The Northwind
and Pubs sample databases from Microsoft might give you some ideas too.
I think you will grasp these concepts pretty easily given that you have
already discovered the pain of redundant data in your table.

Also, there are templates for contact databases, but if you study a
little and go through the exercise of refining your table design the
skill will serve you well should you want to continue designing
relational databases on any platform.

We can help you attack the Access user interface stuff once you get the
table issues sorted out. Post back if you need more help!