Hello. A question about designing relationships with an audit log.
I am setting up a HR db. I want to create a table that records actions performed to employees. I am noticing that my relationships are growing more complex and don't want normalization problems long term.
TblEmployees
TblLocation
TblActions
Tbljob
TblLog
The goal is for the log to track what was done, to what employee, and in which location. Later I want to see how many new hires came fom store x, or how many raises emloyee y has had, or when did employee z get promoted.
That puts several tables dependant on two others. Is that a problem?
Eg tblemployess > tbllocation < tblLog
Should I create a seperate table for each action? I.e. new hire, termination If so, how do I deal with the combo box on the form? Since I have a single actions table, my data entry form gives me a combo box with all possible actions. If I split up that table, how do I make the data entry form easy?
thanks in advance!!!
I am setting up a HR db. I want to create a table that records actions performed to employees. I am noticing that my relationships are growing more complex and don't want normalization problems long term.
TblEmployees
TblLocation
TblActions
Tbljob
TblLog
The goal is for the log to track what was done, to what employee, and in which location. Later I want to see how many new hires came fom store x, or how many raises emloyee y has had, or when did employee z get promoted.
That puts several tables dependant on two others. Is that a problem?
Eg tblemployess > tbllocation < tblLog
Should I create a seperate table for each action? I.e. new hire, termination If so, how do I deal with the combo box on the form? Since I have a single actions table, my data entry form gives me a combo box with all possible actions. If I split up that table, how do I make the data entry form easy?
thanks in advance!!!