browse lookup tip

[Kenneth Brody]

Quoting Richard Kreiss (Sat, 23 Feb 2008 19:50:22 -0500):

> Not sure if this is a bug and I think this bit John Esak once.
>
> Browse lookup to a credit header file from a library file.
>
> Display Credit in descending order.
>
> Credit value cr(6,.0)
>
> Use credit header index A on credit #
>
> On prior to executing the browse, cr is set to "2000" to skip any old
> credits.
>
> Problem, when told to display in Descending order, the cursor lands on the
> lowest value displayed at the end of the file.  It then becomes necessary to
> scroll back to get to the newest entry.

I'm not sure what you mean.  Are you saying that the cursor is being placed
on the wrong record?  Can you give an example with values?

> Create an auto index in descending order and one still has the same problem
> no matter what order the browse is told to display the credits in.
>
> Solution using the descending index is to set cr="999999" which is the
> highest value possible,  Then everything works properly.
>
> I will assume that the same applies if one is using a name field, set it to
> "ZZZZZZ" to insure the reverse display is correct.

-- 
KenBrody at BestWeb dot net        spamtrap: <g8ymh8uf001 at sneakemail.com>
http://www.hvcomputer.com
http://www.fileProPlus.com