Browse & index

[GCC Consulting]

I have a browse lookup which accesses index N.

This index is built on two keys, deposit date and group number. When
accessed through the browse, all of the associated records appear.

I created a process which can be called from he had erected containing the
deposit date and group number to update the associated records. The
processing table uses the same index.

The first record is updated and then a getnext and goto loop. The goto run
some checks on the record about to be processed. The checks for the deposit
date, then the group number and if either of these do not match the
processing ends.

When I ran the update, I found that only about a quarter of the records were
updated. I turned on the debugger, I found that after a few records were
processed a record with a different group number caused the processing to
end.

I rebuilt the index and tried the processing again. Again it failed at the
same point. I checked the record causing the problem and all of the
information appeared correct.  

To get this update processing to work, I created a demand index built on the
same keys but with the selection set limiting the records to the one group
that I wanted.

Has anyone run into this situation where a browse displays the proper
records but a processing table using getnext fails?

The lookup value in both cases is lv=deposit_date&group_code


Richard Kreiss
GCC Consulting

Office: 410-653-2813