First of all, I'm not sure whether I need to continue to use this table or not. I could see calculating the holidays on the fly, but is that better and how could I handle whether each holiday has a closed status or not?
My second thought is a tool that aids in inputting the data into the current database table. But then how does this run? A scheduled task that runs once a year? That's not even an option in the CF scheduled task admin and I can barely imagine a piece of code sitting for an entire year with out needing to be modified for some reason or another.
My third thought is a tool in some kind of admin system that a user could run when necessary, but how would this work in such a way that it would be of some help to the user, with out just asking him to input each holiday and it's date? Which would not really be much better then what is done now. Also, how to store the list of holidays, and which ones are closed and how the date for each holiday is calculated (not looking forward to figuring out Easter for this). The real trouble, is that we have no control of the database structure of the main application. But we may be able use a supplementary database. So there may be an end around for this problem.
Where I keep ending up is a nebulous idea about a "Rules Engine" IIRC is what I've read it's called. Where one can define a set of rules that in turn define the steps of a process that are then automatically implemented to create a desired result. But I don't even know where to begin figuring something like that out.
Thus I turn to all the geniuses on this list.
Any helpful suggestions?
Thank You
--------------
Ian Skinner
Web Programmer
BloodSource
www.BloodSource.org
Sacramento, CA
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
