M
mac
We need to set up a database to record the jobs we work on for our
clients and the names and addresses of the people/companies (clients,
contractors etc.) that work with us on these jobs.
Two people have come up with two different designs which I have tried
to illustrate below where L/T = link table.
[NAMES]<-->[L/T]<-->[ADDRESSES]<-->[L/T]<-->[JOBS]<-->[L/T]<-->(back
to)[NAMES]
[PEOPLE]<-->[L/T]<-->[COMPANIES]<-->[L/T]<-->[JOBS]
With this option company and job addresses would be stored in COMPANIES
and JOBS tables.
The first (circular layout) I think is too complicated but it does give
a lot of scope for jobs to have many names and many addresses,
addresses to have many names and many jobs and names to have many
addresses and many jobs.
The second is simpler in my mind as I can relate this better to the
real world as jobs can have many companies and companies have people.
I would be grateful to receive comments from the Access experts here on
which one we should go for.
clients and the names and addresses of the people/companies (clients,
contractors etc.) that work with us on these jobs.
Two people have come up with two different designs which I have tried
to illustrate below where L/T = link table.
[NAMES]<-->[L/T]<-->[ADDRESSES]<-->[L/T]<-->[JOBS]<-->[L/T]<-->(back
to)[NAMES]
[PEOPLE]<-->[L/T]<-->[COMPANIES]<-->[L/T]<-->[JOBS]
With this option company and job addresses would be stored in COMPANIES
and JOBS tables.
The first (circular layout) I think is too complicated but it does give
a lot of scope for jobs to have many names and many addresses,
addresses to have many names and many jobs and names to have many
addresses and many jobs.
The second is simpler in my mind as I can relate this better to the
real world as jobs can have many companies and companies have people.
I would be grateful to receive comments from the Access experts here on
which one we should go for.