I still support an old app in FOCUS Six for Windows!

TABLEF does not allow the HOLD, SAVE, or multiple print commands either.

DST operator does not work for TABLEF
Also, SET EMPTYREPORT = OFF will have no effect in TABLEF command

I can't think of anything else, so I'll state the obvious.

TABLEF has an F and TABLE doesn't

quote:

They report on multipath PRINT requests differently.

TABLE will fill in the columns of the report in parallel; whereas TABLEF will put instances from each child path in a separate set of rows (leaving the other child paths' entries Missing)

Try this w/ TABLE and then w/ TABLEF, to see the diff:

TABLE FILE CAR
PRINT STANDARD WARRANTY BY COUNTRY BY CAR
IF CAR EQ JAGUAR
END

We have a winner! Sorry to take so long to acknowledge but its a timezoned world!

Over to you J.G for the next question...

"Internal Matix" is a misnomer. When is the internal matrix not a matrix?

Just guessing here ...

Whenever there is not an across or fml request in progress ??

When there is only one row and one column?

Nope.
Nope.
Hint: why did the internal matrix have a 2Gb limit

This is a wild guess:

Would it be because it is actually a FOCUS database being built "internally"?

Yes ... almost there ...

Answer:

When it's a multiple-verb request.

As Mickey noted, the 'internal matrix' is actually a Focus database (hence the limit on size).

For a single-verb request, it's a one-segment structure, which can aptly be described as a matrix: ultimately it holds an n-by-m rectangle of data (n = &LINES; m = number of sort + dependent fields). If there was a point in time when Focus did not yet support multiple verbs, then the 'internal matrix' terminology was an apt description up to that point.

But the structure of the internal database for multiple-verb requests has multiple segments -- one per verb, in a single-path hierarchy. (The top segment is keyed to the BY fields of the first verb; successive segments are keyed to their additional BY fields relative to their immediate parent.)

If you HOLD FORMAT FOCUS, the output MFD reflects the segment and field structure of the 'internal matrix' database, so you can verify the above.

(PRINT, ACROSS, COMPUTE, and BY TOTAL entail some variation from or expansion of the above)

Note the clever leveraging of assets: TABLE includes under the covers a MODIFY engine for gathering in the data to be reported.


Have a nice weekend.

This message has been edited. Last edited by: j.gross,

Thanks Jack - does this mean its Mickey's turn?

Both the WHERE clause and the IF statement may be used to select records based on a list of values in a file.

Other than general syntactical differences,

What are the two most important differences between using a WHERE clause versus an IF statement to select records based on a list of values in a file?

1. Syntax:

IF FIELD EQ (FILENAME)
WHERE FIELD IN FILE FILENAME

2. Size of file

IF: 32K
WHERE: 16K

Ginny

Funny enough tho it says file size in manual it is actually 32k records for IF. Never did tests for WHERE.

Ginny,

File size is one of the differences. Although syntax is different, I excluded that as one of the answers.

quote:

Other than general syntactical differences,

The second difference is not so obvious and may not even be documented.

I checked the WF71 Creating Reports manual and the information in the manual alludes to the second difference I'm looking for as the answer.

Sorry, I missed that bit about syntax.

As for the record counts, I was lazy and didn't want to do a lot of number typing.

I looked in the 5.3 manual and there are lots of differences. The only one that caught my eye wasn't actually stated. It said that the IF file could have multiple columns in it as long as the one tested was first. That wasn't mentioned for WHERE which leads one to suppose that the WHERE file can only have one column. But I have not tested this per se and I know that I've used DST to do this which would generate two columns.

The other difference was the special character thing for WHERE in that you had to put quotes around the value in the file.