Contacts Tables

M

MaineCopper

Hello,

Im designing a database for people responsible for applications at my work.
We have three groups, ApplicationOwner, ApplicationOwnerIT,
ChangeControlContact.

I want all the contacts in one table and linking to the application table as
the appropriate people. I set a join from contacts to the three application
table and it would only force it to one of the groups not all three. I then
created three tables with only one field in each, ID field to act as a
passthrough table from contacts to applications but thats not working either,
I have set joins on all of them.

Appreciate any help.
 
M

MaineCopper

Contactrs table is your typical contaqcts with a Contact ID, FName, LName,
Dept, Email, Phone. I an dlinking them to the Application table with the ID
so the Contact ID in the Contacts table points to three seperate fields in
teh Applications table the AppOwner, AppContact, AppChgContact all the
related fields are number fields in a one to many relationship with a join.

If i create reports it comes out with only contacts of the appowner; however,
the AppContacts and AppChgContact have no associations in the reports. I want
to keep just one contact table if at all possible.

Hope this helps if you need more info let me know.

Jeff said:
Can you provide a bit more explanation of what kind of data you are storing
in each table? Can you describe the relationships among these tables?
[quoted text clipped - 10 lines]
Appreciate any help.
 
J

John Vinson

Contactrs table is your typical contaqcts with a Contact ID, FName, LName,
Dept, Email, Phone. I an dlinking them to the Application table with the ID
so the Contact ID in the Contacts table points to three seperate fields in
teh Applications table the AppOwner, AppContact, AppChgContact all the
related fields are number fields in a one to many relationship with a join.

If i create reports it comes out with only contacts of the appowner; however,
the AppContacts and AppChgContact have no associations in the reports. I want
to keep just one contact table if at all possible.

Since each Contact can have multiple Applications, and each
Application can have many Contacts, it sounds like a typical many to
many relationship - right?

If so, you need *a new table*, with just the ContactID and
ApplicationID (rather than three fields in the Contact table).

You can enter data by using a Form based on either the Contacts table
or the Applications table (whichever is appropriate; you might want
both views) and a subform based on the new table, with a combo box
allowing you to select the Application or the Contact.

John W. Vinson[MVP]
 
M

MaineCopper

I thnk you may be right, let me go play with this for awhile and if I need
more help I'll let you know. Appreciate your assistance with this.

John said:
Contactrs table is your typical contaqcts with a Contact ID, FName, LName,
Dept, Email, Phone. I an dlinking them to the Application table with the ID
[quoted text clipped - 5 lines]
the AppContacts and AppChgContact have no associations in the reports. I want
to keep just one contact table if at all possible.

Since each Contact can have multiple Applications, and each
Application can have many Contacts, it sounds like a typical many to
many relationship - right?

If so, you need *a new table*, with just the ContactID and
ApplicationID (rather than three fields in the Contact table).

You can enter data by using a Form based on either the Contacts table
or the Applications table (whichever is appropriate; you might want
both views) and a subform based on the new table, with a combo box
allowing you to select the Application or the Contact.

John W. Vinson[MVP]
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top