Hello to all,
I am at a developers block or just stuck, or maybe just stupid.
With that said I have a question(s)on best approach method.
Users have a collective bargaining agreement(CBA) database. It lists info about the CBA, years covered, who CBA covers, type, etc. They now want to add a salary database that only applys to CBA(s) that have certain members, if it has those members covered under the CBA they want to imput salary data to span the years covered by the CBA, in one year groups.
My question is should I put the salary form as part of the main CBA form? Have a pop-up form to enter salary data. The salary data spans year to year, so one CBA form many span 5 years, therefore the salary data database will have 5 years data, one recond for each year. A one to many relation, I think. I want to make sure I maintain a proper relation model.
Any examples out there I would be real interested in viewing. Always welcome comments or suggestions.
Thank you!
I am at a developers block or just stuck, or maybe just stupid.
With that said I have a question(s)on best approach method.
Users have a collective bargaining agreement(CBA) database. It lists info about the CBA, years covered, who CBA covers, type, etc. They now want to add a salary database that only applys to CBA(s) that have certain members, if it has those members covered under the CBA they want to imput salary data to span the years covered by the CBA, in one year groups.
My question is should I put the salary form as part of the main CBA form? Have a pop-up form to enter salary data. The salary data spans year to year, so one CBA form many span 5 years, therefore the salary data database will have 5 years data, one recond for each year. A one to many relation, I think. I want to make sure I maintain a proper relation model.
Any examples out there I would be real interested in viewing. Always welcome comments or suggestions.
Thank you!