A Microsoft Office (Excel, Word) forum. OfficeFrustration

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » OfficeFrustration forum » Microsoft Access » Database Design
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

One or two tables



 
 
Thread Tools Display Modes
  #1  
Old April 17th, 2010, 09:38 AM posted to microsoft.public.access.tablesdbdesign
Lars Brownies[_2_]
external usenet poster
 
Posts: 157
Default One or two tables

In my recruitment database I have tblJobs, which at some point is linked to
a candidate via a relationship table. There a two category of jobs:

1. Jobs for which we did/do the recruitment.
2. Jobs which the candidate have had in the past (also most of the time
their current job) for which we have not done the recruitment.

The following fields we need for both categories, like:
ID job
Job description
Organisation

The relationship table is like:
ID relation
ID candidate
ID job
Date start
Date end

For category 1 only, we need to store extra information, like salary number
and other parameters. Also we need to be able to store one or more
requirements for every job of category 1. This should be done in an extra 1
to many table.

Category 2 is only used to do searches on candidates' history (on job
description and/or organisation).

I'm puzzled how to make a good database design. I can imagine I could store
category 1 and 2 in separate tables, because otherwise:
1. a lot of fields would remain empty.
2. I always have to to put filters in my queries, to filter out only
category 1. For instance, management reports will be most of the time about
category 1.

If I have 2 separate tables I'm guessing I'd need an extra relationship
table as well. That doesn't feel right.

Can someone give me advice which solution would be best?

Thanks in advance,

Lars

  #2  
Old April 18th, 2010, 06:36 AM posted to microsoft.public.access.tablesdbdesign
Tom van Stiphout[_3_]
external usenet poster
 
Posts: 10
Default One or two tables

Your Relation table doesn't need an ID field if that ID is not used in other
tables. Often you can simply put the PK over both FK fields.

On the two kinds of Jobs: the classic solution is to have another table in a
1:1 relation with the main table, and it would hold the fields that are only
applicable to one kind of job.

-Tom van Stiphout
Microsoft Access MVP



"Lars Brownies" wrote:

In my recruitment database I have tblJobs, which at some point is linked to
a candidate via a relationship table. There a two category of jobs:

1. Jobs for which we did/do the recruitment.
2. Jobs which the candidate have had in the past (also most of the time
their current job) for which we have not done the recruitment.

The following fields we need for both categories, like:
ID job
Job description
Organisation

The relationship table is like:
ID relation
ID candidate
ID job
Date start
Date end

For category 1 only, we need to store extra information, like salary number
and other parameters. Also we need to be able to store one or more
requirements for every job of category 1. This should be done in an extra 1
to many table.

Category 2 is only used to do searches on candidates' history (on job
description and/or organisation).

I'm puzzled how to make a good database design. I can imagine I could store
category 1 and 2 in separate tables, because otherwise:
1. a lot of fields would remain empty.
2. I always have to to put filters in my queries, to filter out only
category 1. For instance, management reports will be most of the time about
category 1.

If I have 2 separate tables I'm guessing I'd need an extra relationship
table as well. That doesn't feel right.

Can someone give me advice which solution would be best?

Thanks in advance,

Lars

.

  #3  
Old April 18th, 2010, 04:47 PM posted to microsoft.public.access.tablesdbdesign
Lars Brownies[_2_]
external usenet poster
 
Posts: 157
Default One or two tables

Thanks Tom.

Lars

"Tom van Stiphout" schreef in
bericht ...
Your Relation table doesn't need an ID field if that ID is not used in
other
tables. Often you can simply put the PK over both FK fields.

On the two kinds of Jobs: the classic solution is to have another table in
a
1:1 relation with the main table, and it would hold the fields that are
only
applicable to one kind of job.

-Tom van Stiphout
Microsoft Access MVP



"Lars Brownies" wrote:

In my recruitment database I have tblJobs, which at some point is linked
to
a candidate via a relationship table. There a two category of jobs:

1. Jobs for which we did/do the recruitment.
2. Jobs which the candidate have had in the past (also most of the time
their current job) for which we have not done the recruitment.

The following fields we need for both categories, like:
ID job
Job description
Organisation

The relationship table is like:
ID relation
ID candidate
ID job
Date start
Date end

For category 1 only, we need to store extra information, like salary
number
and other parameters. Also we need to be able to store one or more
requirements for every job of category 1. This should be done in an extra
1
to many table.

Category 2 is only used to do searches on candidates' history (on job
description and/or organisation).

I'm puzzled how to make a good database design. I can imagine I could
store
category 1 and 2 in separate tables, because otherwise:
1. a lot of fields would remain empty.
2. I always have to to put filters in my queries, to filter out only
category 1. For instance, management reports will be most of the time
about
category 1.

If I have 2 separate tables I'm guessing I'd need an extra relationship
table as well. That doesn't feel right.

Can someone give me advice which solution would be best?

Thanks in advance,

Lars

.

 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 03:25 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.