Monitoring dates

[lushh]

i've been working on a database that can track the contract dates of contractual employees in our company. do you have any idea on how am i going to structure a table that will include the following:

- The start date of the previous contract
- The end date of the previous contract
- The start date of the present contract
- The end date of the present contract

employees can be issued more than 1 contract.

i'd really appreciate your responses. thank you.

 

[raskew]

Hi -

Can more than one employee be connected to the same contract?

Bob

 

[lushh]

yes, it is possible that two or more employees can have the same contract start and end dates.

 

[raskew]

Hi -

I probably didn't state that clearly. What does a contract represent? Is it a one-time thing with a particular employee -- or -- a piece of work that could involve more than one employee. In other words, could more than one employee be associated with the same contract ID?

Bob

 

[Banana]

One thing I could point out- You don't really need to have "previous contract date" and "present contract date"- that would violate normalization. You really only need startdate and enddate and maybe a yes/no field to indicate whether the contract is current or completed or something like that.

Reading up on normalization will be very helpful in getting right design for your database.

 

[lushh]

Hi -

I probably didn't state that clearly. What does a contract represent? Is it a one-time thing with a particular employee -- or -- a piece of work that could involve more than one employee. In other words, could more than one employee be associated with the same contract ID?

Bob

every employee has a unique contract. that is my problem. and i need a database that can track and can show all the contracts of an employee.

thank you for the response.

 

[raskew]

OK -

Look at Banana's response. I'm not going to repeat it because he's pointed out the way to go! If, however, there were contractID's that involved more than one employee, that would take a slightly different approach.

Post back if you have problems.

Bob

 

[lushh]

ok. i do apologize. this is my first time to create a database. how can i make a relationship between employee id and the contracts?

 

[lushh]

One thing I could point out- You don't really need to have "previous contract date" and "present contract date"- that would violate normalization. You really only need startdate and enddate and maybe a yes/no field to indicate whether the contract is current or completed or something like that.

Reading up on normalization will be very helpful in getting right design for your database.

thanks. yup, i've been reading about normalization, but it's really kinda confusing. this is my first time to create a database. i'm sorry.

 

[Banana]

No need to apologize. This is why we have the forum in first place.

When you have more specific questions, let us know and we'll help you further along.

 

[lushh]

No need to apologize. This is why we have the forum in first place.

When you have more specific questions, let us know and we'll help you further along.

thanks for being so accommodating...