Morning All,
This is a philosophical question, although I suspect the roots of this inquiry lie in performance.
I have a table whose "lot in life" is to manage formal request from the field to do a specific job. That’s the easy part.
Management wants to incorporate a task management list as well and they want it to be in the same view (subform).
So I could add a couple of fields to the tblRequest and it will work for both the formal request and the daily ancillary task that the staff need to perform.
Which would you do; make a separate table and Union Join them in a subform or create more fields in the Request table to manage the extra task?
I’m not sure there’s a “right answer” here, I think it will depend on which method will produce the highest performance over the long run.
This is a philosophical question, although I suspect the roots of this inquiry lie in performance.
I have a table whose "lot in life" is to manage formal request from the field to do a specific job. That’s the easy part.
Management wants to incorporate a task management list as well and they want it to be in the same view (subform).
So I could add a couple of fields to the tblRequest and it will work for both the formal request and the daily ancillary task that the staff need to perform.
Which would you do; make a separate table and Union Join them in a subform or create more fields in the Request table to manage the extra task?
I’m not sure there’s a “right answer” here, I think it will depend on which method will produce the highest performance over the long run.
Last edited: