Validation within a MSG command. (AREV Specific)
At 25 APR 2001 10:35:15AM Michael Slack wrote:
I'm working on an AREV 3.11 application. I just ran across a piece of code that uses validation within the MSG() command. In reading about it, it seems straight forward but when I went to test it for a date entry, it didn't work quite the way I expected. Here is what I'm trying to do.
* THE FIRST THREE LINES WE HAVE IN A COMMON THAT WE USE ALL OF THE * TIME.
MSG_MAP_RC='
MSG_MAP_RC=RC'
MSG_MAP_RC=1
* THEN IN ADDITION, I SET THE VALIDATION.
MSG_MAP_RC=(D)'
BEG_DATE='
MSG('ENTER DATE.',MSG_MAP_RC,BEG_DATE,'')
In my testing, I could enter dates in the DE (01 MAR 1992) and DH (MAR 01 1992) formats and it would take them just fine. Even with some slight variations in spacing and what not. When I entered dates in the other formats (DF, DG, DI, DJ), I got an error message saying that the date wasn't recognized and it needed to be in MM DD YY format. I replaced the the '(D)' with a '(DF)' in the message mapping and it then would take that format just fine but not others. I even tried to put two different validations together trying to make then act as if they had an OR between them but no luck there.
Is there any way to put a date validation into this message mapping that will allow my users to enter any valid date format? I can see this as been a very useful feature.
Thanks for your time.
Michael Slack
At 25 APR 2001 03:12PM Don Miller - C3 Inc. wrote:
Michael..
I seem to recall that this was a bug in AREV 3.11 which was fixed in AREV 3.12. I tested it there just now and it works fine in virtually all date formats. I don't have 3.11 around to play with.
Don't know what else to say. There were several other things that got fixed in 3.12. I would recommend an upgrade.
Don Miller
C3 Inc.
At 25 APR 2001 06:07PM Donald Bakke wrote:
At 25 APR 2001 06:08PM Donald Bakke wrote:
Don,
I tried it in 3.12 and got the same problems. Are you sure you tried DF? (i.e. MAR 1992 01)
At 26 APR 2001 08:59AM Don Miller - C3 Inc. wrote:
Don ..
You're right! Since my customers only enter dates in US format I tested the following:
01012001 -] works
01JAN2001-] works
JAN 1st 2001 -] works
JAN1 -] works (assumes 2001)
01/01-] works (assumes 2001)
01/01/01-] works
* variants of the same with different punctuation (-.,) all seem to work. My users don't use Euro dates or variants thereof so I didn't test those).
Don M.
At 27 APR 2001 09:34AM Michael Slack wrote:
Thanks for the info. I didn't think of the default setting of the date format as playing a part but it makes sense.
Michael Slack