<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">While I agree with the previous reply to not allow that much flexibility, if your users insist, then don’t make this a date field, make it a text field. Unfortunately, I don’t believe that QUICK will allow multiple date input formats. Take the text, extract the date, and issue an error if it’s not a valid date field. Of course to properly test whether it’s a valid date, you’ll have to check the month value and the corresponding correct day value. And don’t forget about Y2K rules.<div><br></div><div>Much easier to restrict what they can enter. Note that they can enter a date with or without the separator, but it must be the separator specified either in the dictionary or on the FIELD statement.</div><div><br></div><div>Bob<br><div><br><blockquote type="cite"><div>On Dec 8, 2022, at 1:15 PM, RUTMJVA <tmjva23664@gmail.com> wrote:</div><br class="Apple-interchange-newline"><div>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div text="#000000" bgcolor="#FFFFFF">
<font size="4"><font face="monospace">If this is quick, my guess
this is also a screen.<br>
<br>
Don't give users ideas. Give them 3 defined fields: yyyy,
mm, and dd<br>
<br>
Then separate the fields with a character of the programmer's
choice.<br>
<br>
They won't be able to touch that character, either dots, dashes,
or slashes, they are simply displayed between fields.<br>
<br>
Then behind the scenes, concatenate the three fields together
into a new field to make a date.<br>
</font></font><br>
<div class="moz-cite-prefix">On 12/8/22 13:02, James B. Byrne wrote:<br>
</div>
<blockquote type="cite" cite="mid:70516d938d46eb8e4dd0011212145e0b.squirrel@webmail.harte-lyne.ca">
<pre class="moz-quote-pre" wrap="">PH839
I have a request to allow users to input dates as in any of the following forms:
yyyymmdd
yyyy.mm.dd
yyyy-mm-dd
yyyy/mm/dd
To handle this I tried the following:
FIELD INPUT-DATE OF TRANSACTIONS
PROCEDURE INPUT INPUT-DATE
BEGIN
LET QKT-TEXT=TRUNCATE(LJ(FIELDTEXT))
IF MATCHPATTERN(QKT-TEXT,"####.##.##") OR &
MATCHPATTERN(QKT-TEXT,"####-##-##") OR &
MATCHPATTERN(QKT-TEXT,"####/##/##")
THEN LET FIELDTEXT = QKT-TEXT[1:4]+QKT-TEXT[6:2]+QKT-TEXT[9:2]
END
Which does not work. If yyyy.mm.dd is input then the error " This entry must
be a date." appears. I speculate that this means that the FIELDVALUE is not
being changed as a result of manipulating FIELDTEXT.
SO, is there any way to implement this feature and if so then what is it?
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Tracy Johnson
BT
NNNN</pre>
</div>
-- <br>= = = = = = = = = = = = = = = = = = = = = = = = = = = =<br>Mailing list: powerh-l@lists.sowder.com<br>Subscribe: 'subscribe' in message body to powerh-l-request@lists.sowder.com<br>Unsubscribe: 'unsubscribe <password>' in message body to powerh-l-request@lists.sowder.com<br>https://lists.sowder.com/mailman/listinfo/powerh-l<br>This list is closed, thus to post to the list you must be a subscriber.<br>Add 'site:lists.sowder.com powerh-l' to your search terms to search the list archive at Google.</div></blockquote></div><br></div></body></html>