D
DonAdd via AccessMonster.com
I am new to MS Access 2007 but worked with an xBase product named Alpha 4
over 20 years ago; needless to say I am a novice when it comes to RDBMS
design and development. I am attempting to design a simple tracking system
for a small consulting unit which tracks information regarding the unit's
projects.
I have three tables:
(1)‘Engagement’ table which holds records with fields containing data
specific to the consulting project (i.e. project start date, project end date,
project type, etc.).
(2)‘Contacts’ table which holds records of people who are associated with a
specific project including customer-side folks, consultants within my small
team and third party contractors if needed. Fields are typical contact
fields including Last Name, First Name, Company, Cell Phone, etc.
(3)'Engagements and Contacts (a Transition Table) which is on the 'many' side
of a one to many relationship w/'Engagement' table via the Engagement Table
Primary key (Engagement ID). This table is also on the 'many' side of a one
to many relationship w/'Contacts' table via the Contacts table Primary key
(Contact ID).
I’m attempting to develop a Form which:
(1) lists information from the single Engagement table on the top part of
the form and
(2) lists multiple records from the Contacts table (I'm assuming adding a
subform is the proper approach) of the various people associated with the
single engagement. Ideally I’d like the user when populating the subform be
able to search for a contact name by last name, first name and company within
a drop down box and if present, select it and have the related information
(cell phone, title, etc.) listed within the subform area.
The associated process would work as follows:
1) User opens Engagement Form (based on Engagement Table) and enters
information specific to the engagement (project start date, project type, etc.
)
2) User would then enter the subform area and lookup and select the specific
contacts associated with the engagement. These contacts will most likely
grow as the project progresses. If the Contact isn't listed within the
lookup function, the user can exit the engagement form and populate a form
for the contact table.
My initial thought is to create a Form based on the ‘Engagement’ table with a
SubForm section for the ‘Contact’ table. Specific to contacts, my problem if
I go this route is how do I create the search/lookup functionality to ensure
a user doesn’t enter a contact twice? I think the correct way to go would be
to use a combo box, but I'm not sure how to do this.
Any guidance is appreciated.
over 20 years ago; needless to say I am a novice when it comes to RDBMS
design and development. I am attempting to design a simple tracking system
for a small consulting unit which tracks information regarding the unit's
projects.
I have three tables:
(1)‘Engagement’ table which holds records with fields containing data
specific to the consulting project (i.e. project start date, project end date,
project type, etc.).
(2)‘Contacts’ table which holds records of people who are associated with a
specific project including customer-side folks, consultants within my small
team and third party contractors if needed. Fields are typical contact
fields including Last Name, First Name, Company, Cell Phone, etc.
(3)'Engagements and Contacts (a Transition Table) which is on the 'many' side
of a one to many relationship w/'Engagement' table via the Engagement Table
Primary key (Engagement ID). This table is also on the 'many' side of a one
to many relationship w/'Contacts' table via the Contacts table Primary key
(Contact ID).
I’m attempting to develop a Form which:
(1) lists information from the single Engagement table on the top part of
the form and
(2) lists multiple records from the Contacts table (I'm assuming adding a
subform is the proper approach) of the various people associated with the
single engagement. Ideally I’d like the user when populating the subform be
able to search for a contact name by last name, first name and company within
a drop down box and if present, select it and have the related information
(cell phone, title, etc.) listed within the subform area.
The associated process would work as follows:
1) User opens Engagement Form (based on Engagement Table) and enters
information specific to the engagement (project start date, project type, etc.
)
2) User would then enter the subform area and lookup and select the specific
contacts associated with the engagement. These contacts will most likely
grow as the project progresses. If the Contact isn't listed within the
lookup function, the user can exit the engagement form and populate a form
for the contact table.
My initial thought is to create a Form based on the ‘Engagement’ table with a
SubForm section for the ‘Contact’ table. Specific to contacts, my problem if
I go this route is how do I create the search/lookup functionality to ensure
a user doesn’t enter a contact twice? I think the correct way to go would be
to use a combo box, but I'm not sure how to do this.
Any guidance is appreciated.