Just a word of caution - - one situation where you will have to switch your Long Date Style setting back to its old default of "dddd,MMMM dd,yyyy" is when using Windows Explorer to copy files.
If you are ever in danger of overwriting another file by copying an earlier version with the same name, Windows Explorer will display a pop-up screen that asks:
This folder already contains a file called 'abc.xyz'. Would you like to replace the existing file, nKB, modified on Monday, July 29, 2002, 10:30:26 AM with this one: mKB, modified on Friday, July 26, 2002, 6:17:26 PM?
However, when you have made the Monarch-enhancing change in your Long Date Style setting to "MMM-yyyy" (described in my earlier post, above), Windows Explorer will now ask:
Would you like to replace the existing file, nKB, modified on Jul-2002, 10:30:26 AM with this one: mKB, modified on Jul-2002, 6:17:26 PM? :confused:
In this one case - - and there may be others of which I am not yet aware - - you will simply have to switch the Long Date Style setting from its Monarch-friendly version of "MMM-yyyy" back to the default setting of "dddd,MMMM dd,yyyy" just for the duration of your Windows Explorer work, and then switch back to "MMM-yyyy" when you are finished. It's a small price to pay for the benefit gained in using Monarch!
Several questions were sent to me directly that asked about specific date examples and how to get to the calculated month field described in the earlier posts. While there is no way to cover all of the situations, one of the questions hit a very good point, namely, what to do when your original report starts out with “real” dates, e.g., 07/14/02, instead of just a text date of “Jul-14-02.” All of my earlier advice had assumed people would start out with original text dates, as do my own example Oracle reports.
If your report starts out with a “real” date, e.g., 07/14/02, you simply use a two-step version of the formula listed. First, if your 07/14/02 date field is called, e.g., Orig_Date, then use the date-to-character function to turn it into a text date:
Because of the mm/dd/yy format, use a modification of the dd/mmm/yy formula used in my original tip:
This should give you the “real” date of 07/01/02 that can be translated to Jul-2002 by the change in Windows Regional Date Setting. The messy substring formula takes any text date of "mm/dd/yy" and changes it to a text date of "mm/01/yy," then Ctod changes it to a “real” date of mm/01/yy. Again, all records within a specific month will have a field of mm/01/yy that will show up as mmm-yyyy after the regional settings change.
As always, feel free to write me if my examples are not clear. :confused: