@RECCOUNT IN 3.5 (OpenInsight Specific)
At 30 JAN 1998 03:54:13PM Paxton Scott wrote:
After a Select or a Select By, @RECCOUNT is 1.
In AREV it showed the number of record keys selected.
How do I get the total selected so I can set my gas gauge?
Thanks for anyone's help
–Paxton
At 30 JAN 1998 04:11PM paxton wrote:
I found get.recCount That will work this time as I'll selecting the whole table!
At 31 JAN 1998 11:26AM Cameron Revelation wrote:
Paxton,
After a Select or a Select By, @RECCOUNT is 1.
@reccount should be set after a select is resolved. Select by, for example, should always set @reccount. The simple select that takes a file handle as an argument does not set @reccount. Also, R/List should set @reccount, since it results in a resolved select.
Cameron Purdy
Revelation Software
At 02 FEB 1998 11:24AM Paxton Scott wrote:
I counld't get it to resolve with a select by either?? I used null sort, etc, cause all I wanted to do was select and process the whole file. But, I found the Get.RecCount routine and that served my purpose ok. Thanks for the reply.
At 05 FEB 1998 09:51AM Aaron Kaplan wrote:
If you get a copy of the Sprezzatura Electronic Newsletter (SENL) Vol 1, Issue 10, you'll find a little article about the reduce in there. There's a subroutine, REDUCTION_TEST. Look through that code. What I left out was that in the part where it's doing the readnext and appending the keys to the list var to write out, the system is setting @REC.COUNT += 1. That's how this var gets updated.
All this boils into resolved and latent selects, which might be the next topic on the list. Don't know, since it changes so much from version to version sometimes. Anyway, unless the statement is fully resolved, it does not know the key count becuase it has not determined all the keys. Bys are almost always fully reduced. Withs are generally not, unless there are indexes used.
Resolved lists means the system has already performeed a readnext or pulled all the keys from the indexes. It writes the keys out to a temporary list file. Since it has them, it counts them for you.
Latent lists mean the system has created a set of reduction criterea. As you readnext through, the system goes through the file, group by group, returning all the keys in that group that match the criteria. Since it does not know if the key should be returned until it's reached it, it does not know the count.
Select statements from the RLIST routine are always resolved (unless you use the LATENT keyword) so they always return @RECCOUNT.
apk@sprezzatura.com
