Hi Peter,
You might think about doing this backwards to the way you state.
1. Create a table of holidays rather than work days.
2. When you are creating a scheduling event, this is a new scheduling
record, plunk the data into global fields first. Then test the event
to see if it is on a holiday before committing it to the database.
3. You need a relationship between your global date and your holiday
table dates.
4. Once the data is placed in the global fields, if the relationship
exists, then this is not an applicable date for creating a scheduling
event and the record is not created. Otherwise a script then creates
an record.
5. This acts as a test on record formation and only creates records
in the proper days.
6. Billings, wages etc. are based on the actual events scheduled.
As I do not know exactly what you are doing, I am talking in the most
general of terms. The idea is to have a table of events that can then
be displayed as a calendar or in lists or used for reporting purposes.
The Holiday table just prevents events from being scheduled on that
day. Or conversely, allows events on that day, but assigns a higher
wage rate to them ... What ever works.
HTH
Dave McQueen
First of all let me thank all that responded to my "I'm at a lost"
post, "Database Sluggish Post" etc. Posts. I tried your ideas but
I'm afraid that I corrupted the database when I forced quit after
realizing the calc change was going to take 2 days to make (maybe a
slight exaggeration). But now I am reconciled to the fact that the
only salvation I have is to rebuild.
So to that end I'd like to ask how others might go about setting up
a scheduling database that requires work days and a special
consideration for holidays? Since that is the biggest portion of the
database. I currently use a calendar table that doesn't have
weekends or the special holidays that are in academia listed. By
using "Lookup next" calcs and straight Look up fields the correct
date is entered and then adding the appropriate number of work days
to the calc I can go to the next date. This goes on for 11 date
fields ( maybe a clue to the lengthly recalculation time huh?).
Is there a better way? I'm going to start Monday morning after a
weekend of washing my sorrows away.
Again I can't thank you folks enough for your advise.
Peter
--
David A. McQueen
LICHEN Software
Barrie, ON, Canada
705-720-9022
705-728-2289
www.lichen-software.com
