IMO, a table is best because it's easy to add or remove any holidays. For example, I don't get President's Day off. For some, Marting Luther King Jr's Birthday is a holiday. In Utah, July 24th is Pioneer Day. And, if you work for a bank, almost everyday is a holiday.
>
>I remember this being discussed this time last year...
>
>Here it is, it doesn't provide you with any real solution, though. There aren't that many of them (holidays, that is). It seems it wouldn't be that difficult to manually enter them in a table, and copy (change) it from year to year.
>
>Thread #
430637 Message #
430637.
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer