Browse & index

[Richard Kreiss]

> -----Original Message-----
> From: filepro-list-bounces+rkreiss=verizon.net at lists.celestial.com
> [mailto:filepro-list-bounces+rkreiss=verizon.net at lists.celestial.com] On
> Behalf Of Kenneth Brody
> Sent: Wednesday, November 14, 2012 11:05 AM
> To: GCC Consulting
> Cc: filepro-list at lists.celestial.com
> Subject: Re: Browse & index
> 
> On 11/14/2012 10:43 AM, GCC Consulting wrote:
> > 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.
> [...]
> > 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.
> [...]
> > Has anyone run into this situation where a browse displays the proper
> > records but a processing table using getnext fails?
> [...]
> 
> Does the processing change the key field in the lookup file?

No:

Lv=deposit_date&group_code

This is the same value for both the browse and the call process.  There is
no drop function used.

Richard