I'm trying to output 2 BLOBs in a report. I've succesfully made 1 to display, but when I'm trying with 2 WF returns the following message:
(FOC1426) DATA ELEMENT VALUE TOO BIG FOR SEGMENT/FIELD segname/fieldname An error occurred when converting a data item for the field in the segment with the names given in the message. Data could not be converted without truncation from the USAGE to the ACTUAL format. FOCERROR is posted to 1426.
I believe this relates to the internal data structure (the "internal matrix") that TABLE defines and loads in order to build the report. That structure is (or at least used to be) none other than a Focus file. It follows that TABLE requests are subject to a segment size limit of 4096 bytes. (Perhaps Table now uses Xfocus for the internal matrix, but that still would impose a limit of 16k.)
There was a feature added not long ago, to place fields in a U segment where necessary to avoid overflowing the segment-size limit. That feature pertains to HOLD FORMAT FOCUS. But the same considerations apply to the internal matrix, and the same solution should be available.
I would open a case.
- Jack Gross WF through 8.1.05
December 09, 2010, 02:35 PM
Tony A
Hakan,
Just a quick thought and completely out of the air -
If the problem might be what Jack is suggesting, could you use passthru ensuring that the data is in the sort order required for the report and then use TABLEF so that the internal matrix is not used?
T
In FOCUS since 1986
WebFOCUS Server 8.2.01M, thru 8.2.07 on Windows Svr 2008 R2
WebFOCUS App Studio 8.2.06 standalone on Windows 10
December 15, 2010, 05:15 PM
Håkan
Jack and Tony, good ideas, but none of them helped. We had to stick to 1 BLOB. I suppose you could make something clever reading the SQL table once again and then create another url in the report, but imagine the performance........
HåkanThis message has been edited. Last edited by: Håkan,