Talk About Network

Google


Register and Login
Nick
Password
Register create new account Sign up is FREE and you can post replies, new topics, bookmark posts and more!
Recover lost password


Software > Access Table db Design > One table or tw...
Latest [ Topics | Posts ] Archive Post A New Topic Post a Reply
<< Topic < Post Post 1 of 12 Topic 12060 of 12659
Post > Topic >>

One table or two?

by "Leslie Isaacs" <leslie.isaacs@[EMAIL PROTECTED] > Jul 30, 2008 at 12:11 PM

Hello All

I have to create a facility within an existing 'Employee' database to
manage 
employee sickness absence. The data to be input will be the employee's
name, 
and the start and end dates of any sickness absence periods. These dates, 
together with some other 'standing' data held in the existing 'employee' 
table, will be used to calculate certain values for each day during the 
sickness absence period: essentially, each day during the sickness absence

period will have to be annotated as being of one of 3 'types' (denoted as 
"W", "S" or "N"). In addition, each day during the sickness absence period

will be assigned by the user to a 'pay period' (there is an existing table

of 'pay periods'). The rule that determines the 'type' will take account
of 
the length of the absence period, the proximity of other absence periods
for 
that employee, and certain other data held about the employee in the 
'employee' table. Once calculated it is im****tant  that the 'type', and
the 
'pay period', that are assigned to each day during an absence period are 
saved so that their values can be retrieved in the future. They cannot 
always be re-calculated because some of the data used in the calculations 
may change (primarily the data range of the sickness absence itself) - but

the results of the original calculation must be retained.

The main output needs to be a re****t showing, for a selected employee and 
selected date range, every date between the selected date range, with each

date being displayed either with its 'sickness type' etc. if that date IS 
during one of the employees absence periods, or with no 'type' etc. if it
is 
NOT during one of the employees absence periods. The actual layout of the 
re****t must be to show the absence 'type' (in the case of absence dates),
or 
a blank field (in the case of other dates) for complete weeks horizontally
- 
e.g. with field names:

 "Sun", "Mon", "Tue", "Wed", Thur", "Fri", "Sat", "Week ending"

the re****t might look like:

      W    W    S    S     N    N    26/07/08
S    S    N    N    N    N    N      02/8/08
                                                    07/8/08
                                                    14/08/08
N    N    N    N    S    S    N        21/8/08

The first row above would represent one blank representing 20/08/08, two 
"W"s representing 21/08/08 and 22/08, two "S"s representing 23/08/08 and 
24/08/08 and two "N"s representing 25/08/08 and 26/08/08. The third and 
forth rows represent week with 7 'blanks' - i.e. these weeks contain no 
dates that fall within any sickness absence period for the employee.
The assigned 'pay period' would not be included on this re****t.

My initial plan was to have a table 'sickness_periods', containing just
the 
employee name and the start and end dates of each sickness period, plus a 
table 'sickness_days', containing the results of the calculations. Now I
am 
wondering whether I shouldn't bother with the first 'sickness_periods' 
table, and instead just enter the data range into two unbound fields on
the 
data entry form, do the calculations and then save the results to the 
'sickness_days' table.

In writing the above I can see that my question may have become too long
to 
get responses from this forum! Obviously I don't expect anyone to give me 
all the answers - I'm just looking for some advice about which way to go 
with this, as I think I'm in danger of getting it horribly wrong! Any 
general pointers would be very much appreciated.

Many thanks
Leslie Isaacs
 




 12 Posts in Topic:
One table or two?
"Leslie Isaacs"  2008-07-30 12:11:01 
Re: One table or two?
Michael Gramelspacher <  2008-07-30 10:20:34 
Re: One table or two?
Michael Gramelspacher <  2008-07-30 14:15:29 
RE: One table or two?
=?Utf-8?B?S2xhdHV1?= <  2008-07-30 10:47:02 
Re: One table or two?
"Steve" <non  2008-07-30 15:58:22 
Re: One table or two?
"Leslie Isaacs"  2008-07-31 10:21:34 
Re: One table or two?
"John... Visio MVP&q  2008-07-31 09:58:38 
Re: One table or two?
"Steve" <non  2008-07-31 10:24:28 
Re: One table or two?
"John... Visio MVP&q  2008-07-31 10:51:04 
Re: One table or two?
"John... Visio MVP&q  2008-07-31 10:47:03 
Re: One table or two?
"John... Visio MVP&q  2008-07-31 17:10:34 
Re: One table or two?
"Leslie Isaacs"  2008-08-01 06:23:01 

Post A Reply:
  Go here to Signup

AddThis Feed Button


About - Advertising - Contact - Frequently Asked Questions - Privacy Policy - Terms of Use - Signup

Contact
tan12V112 Mon Dec 1 22:46:43 CST 2008.