I didn't say nor mean to suggest that it was not _at all_ useful. I have used such an example before myself. I was just recognizing and agreeing with Glenn that there remain some, perhaps several, situations and conversion codes where it is not really too helpful, and could perhaps be enhanced. But also trying to point out that it was indeed not 'broken' per the documentation.
Richard B. Lewis Sr. Software Engineer Dynix rlewis at dynix dot com p 801-223-5392 f 801-223-5202 www.dynix.com -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Janke, Mark There's a very good reason why it works this way. Suppose you have the following LIST statement: LIST EMPLOYEE.FILE WITH HIRE.DATE > "<<Enter Hire Date,(D)>>" Mark -----Original Message----- Glenn wrote: Well, according to the documentation you can specify a conversion code: <<A,PROCESS?,(MCU)>> which should apply the conversion code to the input value, but which appears not to work. Richard's response: I'm on UV 10.0.13 at the moment and the 'HELP <<...>>' says, in part, "The conversion only verifies the format of the data entered. It does not convert the data. If the data does not match the conversion, the user is prompted to reenter it." So I would suggest that, while I agree that it may not be very useful, it does appear to work as the 'documentation' describes it should. ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
