|
Rob, User defined edit codes are (UDECs) used at compile time, no runtime. So, unless you're modifying the vendor's code, it's not a big deal. There are other issues w/ UDECs, such as there are a very limited quantity, they system wide, etc. But is still doesn't address the original question, which is how to define a screen so that the special characters are embedded in the field, but skipped over, so that they don't have to be keyed by the user and will still be displayed? I that that the standard edit codes should do the trick, instead of using EDTWRD, use EDTCDE. -mark Original Message: ----------------- From: rob@xxxxxxxxx Date: Mon, 12 Sep 2005 09:04:58 -0500 To: midrange-l@xxxxxxxxxxxx Subject: Re: EDTMSK and EDTWRD ? I think many shops are loath to use user defined edit codes. Just imagine if vendors used them, and you had two different vendor packages that defined them differently. Egads! Based on that, you might be able to assume that no sane vendor would use them and, thus, you could use them for custom software. So, is that a 180 degree turn or not? Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.