MichaelTamoush
6 years agoQrew Captain
Summing like fields
I'm trying to come up with a creative solution to an issue. Two tables, projects and time cards. Time cards is child.
I have many time cards (hundreds) for dozens of employees (lets say 40). Each time card includes many fields, but for our purposes the important ones are:
Job Number
Time Card Date (will be the end of a week)
Employee ID
If I go to a project, all time cards associated with that project appear. However, as expected on any given project, one Employee may have multiple time cards. I want to get a total hours for that employee. I can sort and group, which shows me the total, but I want it in a field that I can manipulate and use in future scenarios.
All I can think of is utilizing summary fields, but I think I would need to create a summary field for each employee, and have another summary table. Any easier options?
Secondary question: It seems with all these time cards, my table will end up in a couple years with hundreds of thousands of entries. Is there a way to avoid this? Or is that the nature of databases?
------------------------------
Mike Tamoush
------------------------------
I have many time cards (hundreds) for dozens of employees (lets say 40). Each time card includes many fields, but for our purposes the important ones are:
Job Number
Time Card Date (will be the end of a week)
Employee ID
If I go to a project, all time cards associated with that project appear. However, as expected on any given project, one Employee may have multiple time cards. I want to get a total hours for that employee. I can sort and group, which shows me the total, but I want it in a field that I can manipulate and use in future scenarios.
All I can think of is utilizing summary fields, but I think I would need to create a summary field for each employee, and have another summary table. Any easier options?
Secondary question: It seems with all these time cards, my table will end up in a couple years with hundreds of thousands of entries. Is there a way to avoid this? Or is that the nature of databases?
------------------------------
Mike Tamoush
------------------------------