Re: ASCII Control Characters in SQL

["Ryan Hunt" <ryan.hunt@xxxxxxxxxxxxx>]

Thanks guys.  I format in SQL as a last resort so I'm at least judicious
about going at this all wrong.

It would require a lot of brain damage to get the report writer/renderrer to
break apart the string appropriately and display it the way we want it.  I'm
not trying to apply formatting like fonts, bold, etc.  I simply want to
introduce a line break so that typical print programs that respond to ASCII
control characters will show each comment on it's own line.

I think I might have found what I need with SELECT
colXRecordY||(X'0D')||(X'25')||colXRecordY+1 FROM TABLE

I'll know shortly.

Thanks. RH

"Charles Wilt" <charles.wilt@xxxxxxxxx> wrote
in message
news:fa303d750908060630j2f9a4c24ke8c9f832af983d83@xxxxxxxxxxxxxxxxx
Ryan,

IMHO, you're going about this the wrong way.  You shouldn't be asking
DB2 or MS SQL server to format the strings for you.

Instead, whatever application is getting the returned data should
handle formatting the strings.

What application are you using to run the DB2 SQL statement?

If STRSQL, for instance, consider using Query Manager (QM) instead.
QM includes a report formatting capability that includes "word wrap"
functionality.

HTH,
Charles



On Thu, Aug 6, 2009 at 9:03 AM, Ryan
Hunt<ryan.hunt@xxxxxxxxxxxxx> wrote:
> I have a situation where I am using a function to return a formatted group
> of comments per record. In Microsoft SQL I can inlcude ASCII control
> characters (like carriage return line feed) into a string for readablilty.
>
> Does DB2/400 have ASCII control characters SQL commands...or some other
way
> for me to introduce a CRLF via SQL? I need to break the string into lines
> for readablility.
>
> Thanks
>
> Ryan
>
>
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email:
MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.