FW: Browse lookup - odd behavior

[Kenneth Brody]

"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?

-- 
+-------------------------+--------------------+-----------------------------+
| Kenneth J. Brody        | www.hvcomputer.com |                             |
| kenbrody at spamcop.net | www.fptech.com     | #include <std_disclaimer.h> |
+-------------------------+--------------------+-----------------------------+