Focal Point
Large Text Field Handling in new 7.etc versions

This topic can be found at:

November 08, 2005, 02:15 PM
Large Text Field Handling in new 7.etc versions
I have had major difficulties in getting very large text fields to display.

I know the following: Defines can be used to break up the field into 2 or more pieces, and there is a max number of characters allowed per text field.

My experience with large text fields has been:

Defines do not work if the original text field exceeds the max number of characters allowed.

Text field must be the final field displayed on a report. This forces me to work with compounded pdf reports.

Any text field beyond the max length causes WebFOCUS to truncate all report output from that point on. This includes all following compounded pdf reports that have nothing to do with the report that includes the large text field.

My question is: does anyone know of any improvements to the handling of large text fields in newer versions?

Thanks, vickie
November 08, 2005, 02:29 PM
How long is the text field in your database? I believe WebFOCUS can have Alphanumeric fields of up to A4095 since version 4.3.x. Is this long enough to handle your field lengths?
November 08, 2005, 02:53 PM
Unfortunately the text field created by systems is 7,000 in length. Reporting off of the database would have been a great consideration had anyone thought of it when the database was created!

November 08, 2005, 03:33 PM
What is your database and how is it defined? CLOB or VARCHAR? I don't think this format limit for Alphanumerics has been increased in recent releases. Sorry.
November 08, 2005, 05:08 PM
The database is an SQL 2000 with variable characters.

Thanks for responding Mickey...vickie
November 08, 2005, 07:51 PM
Have your DBA create a "View" that breaks the long text field into 2 or more shorter fields.


Or you could possibly use SQL pass-through and do it yourself !!
November 09, 2005, 10:05 AM
Great idea! Thanks, Terry
November 09, 2005, 11:49 AM

Have you tried creating an MFD with a field definition of an A7000 just to see if it would work? Since your SQL 2000 table field is a variable character and not a CLOB it's worth a shot. You can then use WRAP to make the string fit reasonably on a report.

January 26, 2006, 02:57 PM
I just came across an issue where if a field has data with more than 1064 characters, and you're creating a PDF - the job agent will crash. It's not a problem with HTML or Excel output - only PDF's. I don't think it's an issue on 7.1.
January 27, 2006, 07:10 AM
Lenny Ward
What width are using to wrap the column? Are you outputing portrait or landscape?


(Production: WebFOCUS 7.1.3 on Win 2K/IIS 6/CGI)
(Test: WebFOCUS 7.1.3 on Win 2K/IIS 6/CGI)
January 27, 2006, 07:40 AM
The WRAP and paper orientation have no impact - tried 'em all.

We're starting to test WF 7.1 and when I ran the same program on 7.1 it ran without any issues so I'm pretty sure it's a bug and I've placed a case with IBI.

I also tried -READing it into a variable and placing it in a HEADING/SUBFOOT and it crashed as well.

It's pretty much a showstopper for the application I'm working on and I've tried everything I can think of.
February 02, 2006, 12:58 PM
Update to my problem with large text fields. A stored procedure was created to break down the text by looking for carriage returns. Actually works very well with the paragraphs staying intact.

Thank you all for your suggestions.