Re: Table Structure
- From: "Justine" <justine.thorpe@xxxxxxxxx>
- Date: 31 Jan 2007 10:51:52 -0800
On Jan 31, 10:12 am, "John Spencer" <spen...@xxxxxxxxx> wrote:
I would think that you would have ONE table - ServiceSuppliers - that had a
field to identify whether the entity was a Consultant, Vendor, or
Contractor. I would think that the three types of ServiceSuppliers would
have many (maybe most) fields in common.
ServiceSuppliers
SupplierID
SupplierName
ContactFirstName
ContactLastName
SupplierAddress - Multiple fields
SupplierPhone - If you need a lot of different phones, this may involve a
new table.
SupplierTaxNumber (Taxpayer ID, SSN, etc)
etc.
--
John Spencer
Access MVP 2002-2005, 2007
Center for Health Program Development and Management
University of Maryland Baltimore County
.
"Justine" <justine.tho...@xxxxxxxxx> wrote in message
news:1170259919.115876.125110@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hello,
I am reconstructing a database I built a short while ago (not very
good). The purpose of the database is to track construction projects
and all costs associated with each project. Currently I have many
tables, but my concern right now is three tables I have:
ConsultantInfo, ContractorInfo, and VendorInfo
Whenever I send an approved invoice to our finance department for
payment I enter the invoice into an invoice tracking form. The costs
are then associated with the project. My problem is that we make
payments to consultants, contractors, and various vendors that are
neither consultants or contractors. I need to have a table to collect
contractor and consultant information (each set of information unique
from the other) so therefore the two tables. What I currently have
set up is redundant - I also have a vendorinfo table that contains
vendor (non consultant/contractor) information, as well as all the
contractors and consultants. I then use this table as a combo box in
my invoice tracking form.
Does anyone have any suggestions for what a better approach might be?
I thought about creating a query that contains the names from all
three tables and then creating a subform (which I don't really want to
do)based on the query to put on my form...Any suggestions??
Thanks in advance for any insight
Justine- Hide quoted text -
- Show quoted text -
Hi John,
Thanks for the response..Actually that is what I had originally, but I
changed it as I found the information I had to keep on consultants and
contractors (were they prequalified, what was their prequalification
date, expertise, etc.) was quite different and more extensive than the
information I needed to keep on vendors so I split the tables. I
can't think of a way to 'link' all the additional info I need to keep
on the contractors and consultants (which is different from each
other). Maybe I am missing something really basic?
Justine
.
- Follow-Ups:
- Re: Table Structure
- From: John Spencer
- Re: Table Structure
- References:
- Table Structure
- From: Justine
- Re: Table Structure
- From: John Spencer
- Table Structure
- Prev by Date: Re: Tables/Form
- Next by Date: Re: search results - several fields for LastName
- Previous by thread: Re: Table Structure
- Next by thread: Re: Table Structure
- Index(es):
Relevant Pages
|
Loading