What is the maximum number of COMPUTE columns, that can be present in a TABLE FILE Request. ?

As such Is there any limitation on that ?

In one of our reports, we need to have more than 580 compute columns, and then do a COLUMN to ROW conversion using MORE command... Will that be working out ?

This message has been edited. Last edited by: Kerry,

There are limits, so much is true. And they may differ from release to release.
I'd try searching the ibi tech support site for 'limit', and otherwise open a case, specifying the release that you need the limits for. I know that for later releases the number of fields that can be handled has been increased dramatically, but I really can't remember the exact number.

Thanks Gamp, for your reply. It will be much much helpful, If you get me the exact number of COMPUTE Fields, that can be present in a single TABLE File request.

quote:

search the ibi tech support site

It should give you a far better answer than I can provide. Alternatively, open a case with IB and ask for what you need.

Here is some useful stuff, what we have got from IB tech support on this...


-**********-

It is not so much a limit to the number of COMPUTEs - as it is the total
length of all fields.

The total length of all fields in a request can be up to 256K.

The maximum number of fields you can include in a report request is
approximately 1024 (495 for MATCH requests). However, when adding fields to a
request, it is important to be aware that the allowable number of fields
includes all named fields, whether printed or not, including data source
fields, temporary fields (virtual fields and calculated values), certain
internal fields (for example, TABPAGENO), and fields used in headings and
footings.

The total does not include sort fields. This field limit is also affected
by the combined length of fields in the request. Longer field lengths reduce
the total number of printable fields.

When you create a report, the fields specified in the request are stored in a
256K data area (3956 bytes for MATCH requests). The capacity of the data area
is affected by a number of factors:

Every field is rounded up to a full word boundary (a multiple of 4).

Every field is associated with a four-byte counter field, which affects the
total number of bytes in this data area.

Field prefixes and formatting options affect the available data area.

If the combined length of the display fields in the data area exceeds the
maximum capacity, an error message displays. To correct the problem, adjust the
number or lengths of the fields in the request.

This comes from the deep recesses of memory: would the MacGuyver technique be useful here?

HiJimster,

MacGuyver..? Could you please explain how to get along with MCGUY in this requrmnt ?

Ypour initial post indicates that you want to get ROWs from columns; MacGuyver is a great way to generate ROWs.