Re: systems analysis & database design

Your problem is one of analysis - your current results suggest that 'employees' must be existing and current, but your 'jobs' assumes that they must have been current when the job was done. My own resolution would be to use a start / end date for the job and employee and assume in both cases that they need to be concurrent rather than current.

If your design is in the early stages, a rethink of the relationship altogether would be better.

On Mon, 7 Aug 2000 09:41:06 +0100, "the fat heffer" <iamthecow_at_hotmail.com> wrote:

[snip]
>The thing i dont understannd is what happens when an employee leaves, as the
>employee will have no entry on the employee table so when looking back to
>when they did a job their will be no value for the cost of it.
>Please could some one tell me if there is a standard way to get round
>problems like this.

-- 
Mark A Preston BSc, FIAP
The Magpie's Nest
mark_at_mpreston.demon.co.uk