Sure, I'd be interested to see it. Please don't anyone think that what I posted was to illustrate mastery of anything by a master of, well, probably very little if anything. Since I found and adapted this little solution, it seems to be pretty good, especially the Stored Procedure piece (well, I did do that one myself). Usually, I'm the one asking for help, so, this time, I just thought I'd share something that might help others.
I also realized after I sent my last message yesterday that I could add a columns for FiscalQuarters and CalendarQuarters to the PERIODS table. Also, I agree with your approach to formatting/assigning periods. When I use CCYYMM(DD), I am often asked/accused of having resided in Europe (or somewhere not in the USA). Very few understand or appreciate that such encoding still sorts properly even when that data is typed as TEXT. Anyway, yes I would like to see your calculation. Thanks, Steve in Memphis -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Jan Barley Sent: Tuesday, February 26, 2008 6:59 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Fiscal Year/Period Conversion From Date (Table, Data, & Stored Procedure) Steve, Just thought I'd throw my pennies in here! I use a simple calculation to assign a fiscal period to all transactions to compile financials. I simply take the four digit year, multiply by 1000 and add the integer month value. So we would currently be on 200802. This is easy to assign based on a transaction date and calculated at the time of transaction entry without involving a lookup table. In addition to a transaction date (usually invoice date and payment date), I have 2 other fields (IPeriod and PPeriod), depending on if the customer is on a cash or accrual basis. In the company setup, I have the integer month for the first month of the fiscal year and all my calculations for YTD, LYTD, etc. are based on that. I can provide you with the argument I use to calculate that as well if you're interested!!! Jan Barley
