|
Blanks are considered "real" characters (which is why you have to do funny stuff when inserting characters into an update character field). Possible solution: move the database field into a VARYING field and then move it into the DSPF field? How about initializing the DSPF field with some < x'40' value (change the display hardware attributes so you can see the hex values (leading/trailing attributes) of the entry field)? -reeve -----Original Message----- From: midrange-l-bounces@midrange.com [mailto:midrange-l-bounces@midrange.com] On Behalf Of Booth Martin Sent: Saturday, January 18, 2003 2:26 AM To: midrange-l@midrange.com Subject: DDS for DSPF WRDWRAP I have a 480 character field to display. I am using CNTFLD(060) and WRDWRAP which works well when adding new records to the file. However when I get an existing record and write it out the WRDWRAP acts as if it is turned off. If I go to the end of the data and delete the first blank after the last character all works as I expect it to work. Saving the record, then getting it again, the problem reappears. Is this a common experience? Have others solved the problem or have they abandoned using WRDWRAP? --------------------------------------------------------- Booth Martin http://www.MartinVT.com Booth@MartinVT.com --------------------------------------------------------- _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
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.