Hi,

As something of a pet project, I'm looking to develop a tool to track
employee holiday (or vacation for those of us in the US) for my company -
good for the company (if I get something usuable working) and good practice
for me.

Before I even open Access I want to get the relationships sorted.

First looks indicate two basic entities:

Employee
- ID
- Forename
- Surname
- Dept
- other employee details.... etc etc
- holiday allowance (number of days)

Holiday
- Holiday ID
- Employee ID
- Holiday Start Date
- Holiday End Date

Then its a simple one Employee to many Holiday records. Queries can handle
days taken by employee X and so on. Business rules handled by forms (not
letting X take more than their allowance, etc).

Now assuming that is a workable model, what I'd like to do (and this is
where I'm stuck) is to include a feature where I can link employees so for
example, employee X cannot be on holiday if employee Y is on holiday that
date or employee Z is. I.e. with-in a department there may be that only two
of its employees may be off at any one time.

Any ideas? I'm near certain I'm going to require another table linked to
employees but I'm stuck as to how to develop it. Can anyone suggest how I
should develop my table structures. I don't want to be spoon fed but some
pointers in the right direction would be greatly appreciated.

Any and all replies are gratefully received.

Thanks

Chris.

hi.
i've done that already.
post your email and i will sent it to you.
it doesn't do all that you listed but you might be able to
use it as a model and idea getter.
regards

>-----Original Message-----
>Hi,
>
>As something of a pet project, I'm looking to develop a
tool to track
>employee holiday (or vacation for those of us in the US)
for my company -
>good for the company (if I get something usuable working)
and good practice
>for me.
>
>Before I even open Access I want to get the relationships
sorted.
>
>First looks indicate two basic entities:
>
>Employee
> - ID
> - Forename
> - Surname
> - Dept
> - other employee details.... etc etc
> - holiday allowance (number of days)
>
>Holiday
> - Holiday ID
> - Employee ID
> - Holiday Start Date
> - Holiday End Date
>
>Then its a simple one Employee to many Holiday records.
Queries can handle
>days taken by employee X and so on. Business rules
handled by forms (not
>letting X take more than their allowance, etc).
>
>Now assuming that is a workable model, what I'd like to
do (and this is
>where I'm stuck) is to include a feature where I can link
employees so for
>example, employee X cannot be on holiday if employee Y is
on holiday that
>date or employee Z is. I.e. with-in a department there
may be that only two
>of its employees may be off at any one time.
>
>Any ideas? I'm near certain I'm going to require another
table linked to
>employees but I'm stuck as to how to develop it. Can
anyone suggest how I
>should develop my table structures. I don't want to be
spoon fed but some
>pointers in the right direction would be greatly
appreciated.
>
>Any and all replies are gratefully received.
>
>Thanks
>
>Chris.
>
>
>
>.
>

<(E-Mail Removed)> wrote in message
news:438c01c4c686$bc2141f0$(E-Mail Removed)...
> hi.
> i've done that already.
> post your email and i will sent it to you.
> it doesn't do all that you listed but you might be able to
> use it as a model and idea getter.
> regards
>

Hi,

Thanks for the reply. Assuming that the database is quite small (under 2
megs) my mail address is solace1884 .at. hotmail dot com.

If its over that then let me know and I'll work something out - I'm sure you
understand that I'd rather not mention my main address in Usenet

Thanks again

Chris.