I'm pretty sure the internal select (method 2) selects just the next group
at a time and feeds from that until it needs another. In this method you
can get instant results, pretty much like doing a LIST. So this method
would be good where output is being fed to the crt, and you might not want
to
At 02:16 PM 6/17/2004, you wrote:
[snipped]
Note: SELECT F is a BASIC select, not Retrieve's (not the MV Query
Language's) verb. It does not really select the file, it merely sets
up for the subsequent READNEXTs to truly read the next key. So READNEXT
ID;READ REC FROM F, ID involve going to
Looks like someone has too much time on their hands today
Stevenson, Charles [EMAIL PROTECTED] wrote:Please let me deflect this thread
before it degenerates into a GOTO war.
Which would you suppose is much faster:
1: T0=TIME()
FOR I = 1 TO 100
EXECUTE 'SELECT VOC WITH TYPE = V COUNT.SUP'
LOOP
Looks like someone has too much time on their hands today
Actually, the question grows out of a real need for a phantom to
repeatedly loop through a file all day long. My problem is that the
phantom does not have too much time. I thought the repeated overhead
associated with executing a SELECT