Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

PB not handling <LF> characters in report

Status
Not open for further replies.

Jitwad

Programmer
Sep 8, 2002
13
CA
A little background.....

I have an old PB application (created in 6.5) that prints custom reports (orders, invoices, etc) and resides on a Windows box. It is triggered and has parameters passed to it from a KSH script running on an UNIX box. With me?

When the PB app is triggered it retrieves its data by running PL/SQL stored procedures against an Oracle 9i database which is running on the UNIX box also.

Here is my problem.....

I have a query that retrieves into a nested datawindow for user entered comments. The users enter the data into a Multi-Line Edit, but it is then stored as a single VARCHAR field in Oracle (with <LF>'s delimiting the entered lines). When my PB app retrieves the data from Oracle - it is actually printing the ASCII instead of actually inplementing a line feed.

i.e. instead of:
&quot;My name
is JitWad&quot;

I get:
&quot;My name<LF>is JitWad&quot; (except I get the little ASCII 'square' which I couldn't paste in here)

I realize that Windows requires either a <CR> or a <CR><LF> combination to delimit text lines - so I have tried using a REPLACE command in my PL/SQL to return these. All that happens is PB prints 2 of the little ASCII squares(for a <CR><LF>).

Anyone know how to stop PB from interpreting the embedded <CR><LF> as printable characters?
 
Thanks for the suggestion - but I already tried that. Problem is, the text is not beiogn entered or parsed in PB - so using ~r~n does nothing but actually print '~r~n' to the output.

I missed a couple of things in my first post....

- The comments are entered in a multi-line edit in a different system (COBOL based) running on the UNIX server
- From there they are stored directly into an Oracle 9i DB on the same server
- A job is triggered on the UNIX server that fires the PB Application when it needs to print.
- The PB App (on a separate Windows machine) then retrieves the data from the Oracle DB directly to a datawindow as a result set.
- Then it essentially prints a datawindow preview as a report.

Is there a way to force PB to recognize these retrieved LF/CRLF characters as non-printing characters when they are part of the result set from an Oracle DB?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top