I think someone already mentioned GO BOTTOM. But just in case there is an index set, I think you might want to do a SET ORDER TO 0 just before doing the GO BOTTOM. And of course, if you do that, you might want to restore the index after the GO BOTTOM. Something like:
cIndex = ORDER() set order to 0 go bottom set order to (cIndex) On Wed, Jul 3, 2019 at 12:48 PM Gene Wirchenko <[email protected]> wrote: > Hello: > > I have a situation in my app where I am having to pick up what > will presumably be the last row in a table. Mind you, the general > situation is that it might not be if in a multiuser situation. > > With the current situation, I can use an index to find that row > really fast. > > BUT ... > > What if an index is not appropriate? Is there any way to do a > LOCATE backwards (or something equivalent)? (The table has 186,574 > rows currently so searching backwards would definitely be worth > it.) I do not think there is such a critter, but maybe, you know better? > > Sincerely, > > Gene Wirchenko > > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: https://leafe.com/archives This message: https://leafe.com/archives/byMID/cajgvlx1tfqtg6dpre+k1lbdeuwkkbgxzhjy5mucvon2jyhf...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
