FW: Browse lookup - odd behavior

[Jay R. Ashworth]

On Thu, Jul 15, 2004 at 04:11:42PM -0400, Kenneth Brody wrote:
> "Jay R. Ashworth" wrote:
> [...]
> > > > 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?
> 
> What about records that have been added/deleted since the lookup was last
> run?  Starting at the 37th record is no longer a valid place to start.
> 
> And what about keeping track of dropped records?
> 
> Or are you suggesting actually re-running the lookup in its entirety?

Doing anything else seems semantically inadequate, as this problem
demonstrates.

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