vacation accruals design



hey all,
i was task with tracking vacation hours for each employee in a company. the
way i did it was i calculated the accruals and hours taken on the fly and it
worked just fine. but then some changes came along and the solution
discovered was to save the totals in the database and maintain those fields.

my stored procedure was kinda huge, should that have been my clue that i was
doing so much on the fly? how could i have avoided or forseen this coming?
also, should vacation time accrued and taken been maintained in the database?


Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question