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)>>" If the conversion code in the inline prompt replaced the entered value with the result of the ICONV, the statement would become (assuming 11-AUG-2004 were entered): LIST EMPLOYEE.FILE WITH HIRE.DATE > "13373" 13373 is not a valid external date, so the warning "Bad data "13373" for conversion "D2-". Unconverted data used for selection." is displayed, but the statement returns the proper records because 13373 is already in internal format. Ugly, but correct. However, if you entered the date 10-JAN-1968, the statement would become LIST EMPLOYEE.FILE WITH HIRE.DATE > "10" In this case, there's no warning because '10' is seen as being an abbreviation for the first day of the 10th month of the current - 01-OCT-2004 and is converted to the internal format of 13424 by the LIST processor, resulting in only those employees hired after 01-OCT-2004 being listed. Pretty, but wrong. 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/
