Multiple date input formats for QUICK

[RUTMJVA]

To thrown a monkey wrench into it, the users may also want a space 
delimiter, heh, heh, heh.

Which reminds me of the original MANMAN command line (xx,nnn). VAX 
allowed a dot or a space, HP3000 was a comma, then one day in a later 
version they decided to let both systems use either 3 delimiters.

On 12/8/22 13:39, Robert Deskin wrote:
> 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.
>
> 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.
>
> Bob
>
>> On Dec 8, 2022, at 1:15 PM, RUTMJVA <tmjva23664 at gmail.com> wrote:
>>
>> If this is quick, my guess this is also a screen.
>>
>> Don't give users ideas.  Give them 3 defined fields:  yyyy,  mm,  and  dd
>>
>> Then separate the fields with a character of the programmer's choice.
>>
>> They won't be able to touch that character, either dots, dashes, or 
>> slashes, they are simply displayed between fields.
>>
>> Then behind the scenes, concatenate the three fields together into a 
>> new field to make a date.
>>
>> On 12/8/22 13:02, James B. Byrne wrote:
>>> 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?
>>>
>>
>> -- 
>> Tracy Johnson
>> BT
>>
>>
>>
>>
>>
>>
>>
>> NNNN
>> -- 
>> = = = = = = = = = = = = = = = = = = = = = = = = = = = =
>> Mailing list: powerh-l at lists.sowder.com
>> Subscribe: 'subscribe' in message body to 
>> powerh-l-request at lists.sowder.com
>> Unsubscribe: 'unsubscribe <password>' in message body to 
>> powerh-l-request at lists.sowder.com
>> https://lists.sowder.com/mailman/listinfo/powerh-l
>> This list is closed, thus to post to the list you must be a subscriber.
>> Add 'site:lists.sowder.com powerh-l' to your search terms to search 
>> the list archive at Google.
>

-- 
Tracy Johnson
BT







NNNN

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sowder.com/pipermail/powerh-l/attachments/20221208/9c0e45ce/attachment-0001.html>