[CLOSED]Difference between TABLE and TABLEF

November 13, 2007, 07:49 AM

Gobinath Velusamy

Hi All,

I leanred TABLEF is faster in data retrivel than TABLE command ....

1. What is the main dirrerence betweek thease?
2.What is the limitation when using the TABLEF instead of using TABLE ?

Thanks in Advance
Gobi

This message has been edited. Last edited by: <Emily McAllister>,

November 13, 2007, 08:05 AM

Danny-SRL

Gobinath,
TABLEF does does not create the Internal Matrix which is usually in the file FOCSORT. Hence no sorting is done.
You can use BY's but sorting will not take place.
You cannot use ACROSS, nosplit, DST., EMPTYREPORT, RETYPE.
You cannot use multi-set requests.
However, when you just want to read a file and create a HOLD file, for example, it is very fast.
See also page 17-9 in the 7.6 manual.

November 13, 2007, 03:03 PM

Frans

You can use BY, but since there's no internal matrix the sorting has to be done by the RDMS. So no sorting on defined fields.

July 18, 2016, 07:11 AM

reena

I am using TABLEF instead of TABLE in my focus program because i was getting error " (FOC920) FOCSORT EXCEEDED CURRENT PAGE LIMIT "
But now when i am using TABLEF ,I am getting below error
"(FOC037) THE REQUEST IS INCOMPATIBLE WITH TABLEF"
my program is like :

TABLEF FILE ARRP_BL
HEADING
-INCLUDE gnrphdr.fex
"CYCLE : "COMPANY : -*---"EXCHANGE : " "

SUM GLCODE AS 'ACCT, CODE ' IN 1
-* CATEGORY AS 'CATEGORY, CODE ' IN 12
CATCODE AS 'CATEGORY, CODE ' IN 10
CATDESC AS ' DESCRIPTION , ' IN 24
T_AMT AS ' TOTAL ' IN 49
B_AMT AS ' RECURRING , AMOUNT ' IN 65
P_AMT AS ' PARTIAL , AMOUNT ' IN 81
O_AMT AS ' ONE TIME , AMOUNT ' IN 95
U_AMT AS ' USAGE , AMOUNT ' IN 109
NO_MSGS AS ' # OF, MESSAGES' IN 123

BY DUMMY NOPRINT
BY CYCLE NOPRINT
BY COMPANY NOPRINT
BY NPA_NXX NOPRINT NOSPLIT PAGE-BREAK
BY GLCODE NOPRINT
BY CATEGORY NOPRINT
BY CATCODE NOPRINT
-*--BY CATDESC NOPRINT
-*-

Kindly suggest asap

quote:
Originally posted by Danny-SRL:
Gobinath,
TABLEF does does not create the Internal Matrix which is usually in the file FOCSORT. Hence no sorting is done.
You can use BY's but sorting will not take place.
You cannot use ACROSS, nosplit, DST., EMPTYREPORT, RETYPE.
You cannot use multi-set requests.
However, when you just want to read a file and create a HOLD file, for example, it is very fast.
See also page 17-9 in the 7.6 manual.

July 18, 2016, 08:25 AM

Dave

reena,

hard to tell.

There is some functionality that can't be ( e.g. unsupported ) handled by TABLEF.

Two main suspects : NOPRINT and IN n
[ or whatever there is in the rest of the TABLE request and -INCLUDE ]

What happens if you leave out all that?

July 18, 2016, 10:21 AM

Danny-SRL

Reena,
Welcome to the Forum!
When you show code please use the < / > icon. You then put your code between the generated CODE tags.
As for your problem, it is most probably the NOSPLIT you use in

  
BY NPA_NXX NOPRINT NOSPLIT PAGE-BREAK

Try without it.
Is your output PDF? If not the IN will be ignored.

July 22, 2016, 06:31 AM

reena

Danny-SRL,

I tried after removing NOSPLIT but it is increasing no of output reports.
Suppose my output is 3 reports with NOSPLIT command but after remove this i get 6 output reports.This is because NOSPLIT determines if the total number of lines related to the new value can fit on the current page. If they cannot, the page breaks and the group of lines appear on the next page.

My output is .layout file.

July 22, 2016, 02:30 PM

j.gross

quote:
" (FOC920) FOCSORT EXCEEDED CURRENT PAGE LIMIT "

Go back and see what you can do to avoid that limit.
I shouldn't be reached unless you have a mammoth number of rows (distinct combinations of the sort fields DUMMY ... CATCODE), and/or a mammoth-size record (any A4095's among the sort and verb-object fields?)