Try this trick from
[size="1"][ May 18, 2006, 05:29 PM: Message edited by: Todd Niemi ][/size]
Sandy, I think you actually just wanted to know why the wacky results were coming up for the different settings.
Your original date field has ten alphanumerics - - eight integers and two character symbols (the two slashes). In your four examples:
Your first example does a straight translation of your 10/02/2002 date field to a ten character wide text field. No changes or alterations.
Your second example only uses a template width of eight, and thereby just captures 10/02/20 - - dropping the last two digits of 02. Monarch's default Y2K date logic takes an apparent year of "20" and translates it to "2020." Therefore, you are left with "20201002."
Your third example is what you wanted. The template width of ten captures all ten alphanumerics of your date and displays it in your desired format, namely, "20021002."
Your fourth example only uses a template width of nine, and thereby just captures 10/02/200 - - dropping the last digit of 2. Now, intelligent as Monarch is, the year range it can catch in a yyyy format is 1601 to 2100. In a year format of yy, it can catch 1900 to 2098. In any case, a year of 200 is quite beyond it's recognition. Since it can make no sense of this date, I think you would see "----
" regardless of the display width.
Hope this all makes sense. At least you have your proper solution in your third example.
Thanks for the advertising, Nick! As always, your check is in the mail! [img]tongue.gif[/img]
[size="1"][ October 11, 2002, 08:59 PM: Message edited by: Tom Whiteside ][/size]