🚀 go-pugleaf

In article <1993Jan10.234156.10100@colorado.edu> heuring@riker.cs.colorado.edu (Vincent Heuring) writes:
>
>I am trying to create a date field with a custom date format of the
>kind mm/yy, as in 12/92. I go to the date format in the format menu,
>and create a custom date that looks like: month /  year empty empty empty.
>But when I try to actually enter a date in that form, I get a dialog box
>that says
>
>	"The date in this field must have a valid date in the range of
>	years 1 to 3000, and should look like "12/31/92."
>
>Is this a FMP message, or a system message? The system date format
>does not allow a format of the form mm/yy. The day must always be
>present. Is this a FMP bug, or am I overlooking something?
>

This is a FM Pro message, but I believe it checks your system's international
settings to find the form that it expects.  Changing the Date format
as you describe will only change the way the data is displayed.  FM Pro
doesn't have input filters (unlike 4D).  The only thing FM is smart enough
to do is to add the current year if you leave it off.  So in your example,
it's assuming that you mean 12/92/93, which doesn't make any sense to it.

One way to simulate this is to use a Text field and a Date-Calculation field.
Your calculation would parse the text expression and add "one" for the day
of the month.  It would use the display option that you designed above.
In my opinion, this is a bit too much work.

-Charles
 charlesa@ncar.ucar.edu