Okay. I like the idea of unioning the holidays and events for calculation purposes. Seems a clever way to simplify the caclulation routines, but keep the entities separate for when they need to be. -- Dave Hargis, Microsoft Access MVP "genoki@yahoo.com" wrote: Thanks Klatuu & dch3, I think I have enough to solve my challenge. Klatuu your suggestion to consider Events

Here are two functions. One that calculates the number of working days between two dates. It excludes Saturdays, Sundays, and any date in the holiday table. To add an event table, you could easily copy the code used to count holidays. But, I would suggest that both holidays and events be in the same table as they are logically the same in your case. If you need to differentiate between

Absolutely Beautiful man. Thanks for allllllll of you help! I appreciate it. "Douglas J. Steele" wrote: Unfortunately, you fell victim of wordwrap in what Dave posted (some of his lines of code appeared as two lines in his post). Here's a version that shouldn't have that problem: '---------------------------------------------------------------------------------------

Hmph. I never used the module tab before. I did everything you told me to do and everything seemed great until it told me that the VB Editor had a syntax error in it. What do I do now? "Klatuu" wrote: You bet. First, copy and paste the code into a standard module. That would be: Choose the modules pane in the database window Click new to create a new module - The VB editor

Thank you very much Klatuu. I have no idea how to use this VBA code. I don't know where to put it or what each line means in relation to my data. Can you break this down just a little bit more for me? The furthest I got was adding the holiday table and then everything just went blank for me. I've never studied this part of access that indepthly before. Please help, I'm 80%% done with