FW: Browse lookup - odd behavior

[Jay R. Ashworth]

On Thu, Jul 15, 2004 at 11:42:56AM -0400, Kenneth Brody wrote:
> "Jay R. Ashworth" wrote:
> [...]
> > > Try logging which records you delete, and display the record number in the
> > > browse lookup.  When a "wrong" record appears, check the log to see if that
> > > record was the one you just deleted.  (I'm assuming that the user probably
> > > won't remember the record numbers that were displayed just prior to the
> > > "wrong" record appearing.)
> > 
> > I came in late, but is the lookup index-based?
> > 
> > Cause if it is, I submit that filePro internally caching the record
> > numbers is either a poor design decision, or a bug -- as indicated by
> > the trouble that prompted this thread.
> 
> And what would you cache instead?

Whatever "lookup" information was use to generate the lookup in the
fisrt place, modulo whatever row-count offset has been generates by
user navigation.  That wasn't obvious?

Cheers,
-- jra
-- 
Jay R. Ashworth                                                jra at baylink.com
Designer                          Baylink                             RFC 2100
Ashworth & Associates        The Things I Think                        '87 e24
St Petersburg FL USA      http://baylink.pitas.com             +1 727 647 1274

	"You know: I'm a fan of photosynthesis as much as the next guy,
	but if God merely wanted us to smell the flowers, he wouldn't 
	have invented a 3GHz microprocessor and a 3D graphics board."
					-- Luke Girardi