FW: Browse lookup - odd behavior

[Kenneth Brody]

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

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