RE: DDS for DSPF WRDWRAP

I defy anyone to learn about varying length fields on the InfoCenter.  I
went to the DDS manual, and then decided to search the manual.  Well guess
what - searching the manual is not a choice.   IBM is still on their old
kick of concealing information in the most ingenious ways.

Here's what I was trying to learn:  How do I use a varying length field on a
display file?  Reeve's answer makes sense, so I defined my physical file's
field as 480, Varying.  The Display file references this field.  The dspf
won' compile.

Jon & Susan have  a nice discussion on varying that I found through the
archives but it didn't mention the display file.

---------------------------------------------------------
Booth Martin   http://www.MartinVT.com
Booth@MartinVT.com
---------------------------------------------------------
 
-------Original Message-------
 
From: Midrange Systems Technical Discussion
Date: Saturday, January 18, 2003 08:20:25 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: DDS for DSPF WRDWRAP
 
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
---------------------------------------------------------