Auto pop textbox on 2nd form with same value as 1st form

[Kryst51]

Is your hours planned table going to contain records per employee? How does it fit in.

 

[Arvin]

Hello, sorry for the delay ...

No, the Hours table will not contain any records per employee.... the hours table is only used to populate the Plannedhrs and Actualhrs fields ....

Arv

 

[Kryst51]

Actual hours wouldn't be the same for every employee would it?

 

[Arvin]

Actual hours wouldn't be the same for every employee would it?

Right ...also ....

the hours table is only used to populate the Plannedhrs and Actualhrs fields ....

I meant that the Hours tbl will populate the drop down boxes for Plannedhrs and Actualhrs fields .....

 

[Kryst51]

Ah, I see.

 

[Kryst51]

Do managers and directors also fill out the weekly schedule thing?

 

[Arvin]

Do managers and directors also fill out the weekly schedule thing?

Managers = yes, why ...to update/add new employee tasks

Directors = No, the directors will use this to view reports and activies ....

 

[Arvin]

Managers = yes, why ...to update/add new employee tasks

I forgot to mention ..that the managers will report that they have completed their weekly reviews with thier employees....

 

[Kryst51]

I wasn't sure if managers and directors had to fill it out the same as an employee.

Alright, Go ahead and form your relationships on the relationship screen

Then you can make some basic queries which will make your life easier.

Edit: I suggest enforcing referential integrity when making a link, I am not sure how critical the other two options are, so you might want to read up on that a little.

 

[Kryst51]

I forgot to mention ..that the managers will report that they have completed their weekly reviews with thier employees....

This kind of thing might warrant the addition of more tables. At the very least, your basic structure is more sound. And since it is normalized, adding fields to tables or more tables, won't wreak havoc, at least not at this point. It will towards the end, but now it's good to think about.

 

[Arvin]

This kind of thing might warrant the addition of more tables. At the very least, your basic structure is more sound. And since it is normalized, adding fields to tables or more tables, won't wreak havoc, at least not at this point. It will towards the end, but now it's good to think about.

thats what i started to think after i wrote that .... I will go ahead and ceate the relationships ... and will leave the "manager reporting" out of it for now...

sound a upload the revised db once I'm done?

 

[Kryst51]

Yep, I am working on an idea for you, then you can mull the idea around to see if you like, or at the very least get an idea of the logic behind it.

 

[Arvin]

As requested .... here it is

Also, in regards to the "referential integrity" i did enforce it ... and as for the other 2 options are concerned ...i don't think I require them.

 

[Kryst51]

One more thing. I think you need a junction table between the role and the employee table. That table will contain the employeeID, the roleID and the AsOfDate. plus its own pkautonumberID

 

[Arvin]

One more thing. I think you need a junction table between the role and the employee table. That table will contain the employeeID, the roleID and the AsOfDate. plus its own pkautonumberID

Done !

Here it is ..please advise if this is what you meant ...

 

[Kryst51]

Almost perfect! Rename it with something meaningful, because you technically have junction tables all over the place. Also delete the relationship that is between employee and employee role. Delete out of your employee table the employee role ID and the As of date, as that is now supplied through the junction table link.

No Need to repost the db, I'll fix my copy here

 

[Kryst51]

I think you need to change your hours table to the ID and one field.

tblHours

pkhrsID
Hours

which would contain 1,2,3,4,5,6,7,8, or whatever the options are.

You'll link the weekly schedule table later when designing the form.

 

[Arvin]

...Done and done

 

[Kryst51]

Take a second to backup your db, also compact and repair, I just froze up my comp and lost all of my changes

 

[Arvin]

Take a second to backup your db, also compact and repair, I just froze up my comp and lost all of my changes

OUCH ! ! ! ...thank you for tip ..I just backed it up and ran the compact and repair utility