An intermittant Select problem occurs using Arev 3.12. Conditions are that an Rbasic program has a Clearselect, followed immediately by Select File with Current=1', followed by Savelist, followed by Getlist. Occasionally records with the Current flag set are NOT SELECTED by the select routine. All procedures except the Clearselect are Perform statements. Any ideas on a likely cause.

Regards

Ray

[email protected]

Ray,

How is CURRENT defined? Is it a data column or a symbolic column? Is there an index on this field? Is it possible that the value of this field can change during the processing of the report? What I'm getting at is that maybe at the time the select is run, all current records WERE selected but then as you run the report, the values on some other records changed and that's why they weren't included.

Matt Sorrell

[email protected]

Matt, thanks for your comments, however the process is simplistic in the extreme, the field is a data field, (field 1 of record), the only field by the way. The file is used mainly for referencing the current months data and using the id's to extract data from the historical data file. No indexing, no possibility of change. The process creates the record and sets field 1 to 1, the original calling program then selects the records with 1, saves the list, and there are many records which do not even get onto the list, even though they are correctly present on the file. Strange system this Arev at times.

Thanks and regards

Ray

You stated all statements except clearselect were perform statements. What was the clearselect? If it was an execute, then it effectively does nothing.

Victor,

The CLEARSELECT was just the Rbasic command executed within an Rbasic program, as were the other PERFORMS. Since no Cursorvariable was being used the CLEARSELECT should clear the active current list, well thats the the manual says anyway.

All processing done using Rbasic programs, no windows, indexing etc.

Regards

Ray

If i understood you, i dont have any problems with the series of statements.

Here this is what i tried…

CLEARSELECT

PERFORM 'SELECT VOC WITH TYPE EQ "VERB3"'

PERFORM 'SAVELIST B'

CLEARSELECT

PERFORM 'SELECT VOC WITH TYPE EQ "VERB1"'

PERFORM 'SAVELIST A'

STOP

END

This process got me consistant results. I also tried this too…

First i selected a sample 10 rows. "SELECT 10 VOC". Then i ran this program… "RUN TEST BB".

PERFORM 'SELECT VOC WITH TYPE EQ "VERB1"'

PERFORM 'SAVELIST A'

STOP

END

I got consistant results too.

If you would include the actual code statements so that i can see them, maybe there is some syntax in the statements that is causing the problem. And maybe the table is broken (or damaged).

Richard,

The statements are identical to yours with the exception that I always follow the select with a check on @RECCOUNT for no records selected. As I said the error results are intermittant, these same statements have caused no apparent problems for years, I have noticed only that there is occasionally a missed record, or series of records, not even in sequence, just as if the Select had passed them by. Thanks for your time however,

Ray

View this thread on the forum...