Re: Prompt override program and dates

["Kevin Watkins" <kevinw@xxxxxxxxxxxxxxxxx>]

Just a note... Advanced Systems Concepts (Sequel) does this in their support
of the date data type but I have no idea how. The fields are displayed as
xx/xx/xxxx on the input screen without quotes. You must use quotes in the
sequel view tho around the variable name.   just a thought...



>So long as you want the date separators to appear on the prompt then
>the quotes are needed.  On the prompt display it may appear that you
>can directly key in the separators, but if you do and then use F14 you'll
>see that the prompter is just adding the quotes for you (under the
>covers).  Likewise if you want the separators when specifying the Date
>on a command line prior to prompting, you again must use the quotes.
>
>Without the quotes the system is interpreting the separator as an
>operator, and that's not allowed.
>
>Bruce Vining
>
>>
>>I have a prompt override program, returning a date to a command. The
>>command parameter for the date is defined as:
>>PARM KWD(DATE) TYPE(*DATE) MIN(1) PROMPT('Date')
>>
>>The POP works fine, except that I must return the date inside quote
>>marks: '09/15/1998'. Subsequently, the quote marks appear in the
>>command's input field.
>>
>>I would like to return the date without quote marks, so it appears as
>>Date . . . 09/15/1998   instead of
>>Date . . . '09/15/1998'
>>
>>I tried using EXPR(*YES) on the DATE keyword, but that isn't allowed.
>>
>>Are there any suggestions?
>>
>>Thank you,
>>Loyd Goodbar


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---