Jim Dettman
jimdettman at verizon.net
Tue Oct 9 08:18:17 CDT 2007
Gustav, <<Leery? I wonder why.>> My gut hunch is it would be easy for the calculation logic to be wrong and miss it. It would be something that I would want to exhaustively test. Case in point; it was only seven years ago that a lot of date calculations messed up because they didn't include the third rule for calculating leap years (if it's divisible by 400, then it is a leap year). Then of course a large part of that distrust is probably just old habit; I've been using a lookup table for fiscal dates since my Wang mini days. Just seems a lot simpler and straight forward to me and I've never had a problem doing it that way. So as the saying goes, "If it's not broke...." Jim. -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav Brock Sent: Tuesday, October 09, 2007 5:47 AM To: accessd at databaseadvisors.com Subject: Re: [AccessD] Calculating End of Month on a 4-4-5 Schedule Hi Jim Leery? I wonder why. A function like this will run in microseconds and begs to be wrapped into a callback function as source for your combo. This is a general comment. That said, I still don't get how this 4-4-5 system should be used and calculated, and your comments about weeks at year end seem highly relevant. /gustav >>> jimdettman at verizon.net 08-10-2007 20:05 >>> Besides which with a lookup table, they can implement whatever type of closing schedule they want (monthly or 4-4-5). For myself, I've always used a hybrid approach; I use a lookup table, but fill that table automatically for them with what I believe to be the correct dates based on what they tell me the last day of the week is and what schedule their using. Finial check then is up to them. I'd be leery of using a totally calculated approach. Jim. -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Drew Wutka Sent: Monday, October 08, 2007 12:31 PM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Calculating End of Month on a 4-4-5 Schedule I concur. If you want the last Saturday of any month, I can do that in one line of code, but this 4-4-5 thing is going to shift one day every year (and 2 every leap year). So eventually, you will end up with the start of a fiscal month at the beginning of another month. (Take 2007, if you say that 1-31-2007 is the end of the month, the beginning would actually be 12-31-2006). I'm good at math, but the 4 4 5 thing eludes me how to come up with an equation to calculate it. Seems like the most efficient route would be to just build a look up table. Drew -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Dettman Sent: Monday, October 08, 2007 10:40 AM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Calculating End of Month on a 4-4-5 Schedule It's a standard in the US financial community. It's based on the fact that the year needs to be divided up into 13 week quarters for accounting, yet the calendar varies. The way I typically see this implemented is a table containing the last (or first) fiscal date for each month, and the last day of the fiscal year. It's then easy to determine which month (and hence quarter) a given date falls into. Jim. -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com