So maybe there's a data stacked input? try testing SYSTEM(10) to test the stack and/or put in a CLEARDATA before your field if there is.
Cheers, Stuart -----Original Message----- Yep, it is part of a terminal escape sequence and I actually wrote a subroutine that I called when this occurred that scanned all of common for the escape sequence. I only found subsets of the string, and not the full string that was being inserted into CITEM when the read failed. So it is not coming from another common variable. -----Original Message----- can you ascertain if it's an edit key sequence or a terminal display sequence.. you might get another clue where the value is coming from. ****************************************************************************************************** This email message and any files transmitted with it are confidential and intended solely for the use of addressed recipient(s). If you have received this communication in error, please reply to this e-mail to notify the sender of its incorrect delivery and then delete it and your reply. It is your responsibility to check this email and any attachments for viruses and defects before opening or sending them on. Spotless collects information about you to provide and market our services. For information about use, disclosure and access, see our privacy policy at http://www.spotless.com.au Please consider our environment before printing this email. ****************************************************************************************************** _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
