Can I use "getnext -" in dclerk?

[Jay Ashworth]

----- Original Message -----
> From: "Kenneth Brody" <kenbrody at spamcop.net>

> ObAnswer: "What happened when you tried it?" :-)

I didn't.  :-P

> Longer answer:
> 
> If you read my initial reply to the "get clerk to act like report"
> thread, you would see this:
> 
> > One possibility that comes to mind is to use the selection set to
> > build a
> > demand index. Then use lookup-dash to traverse that index, printing
> > the
> > forms along the way.
> 
> (That is, "yes, you can use getnext-dash to go with the lookup-dash".)

Yes, but I'm not *using* a "lookup -".

The user navigated to the record.  Somehow.  I merely want to move to...

> However, what do you mean by "the next available record in the file"?

the next record in the active navigation index after the record I am
currently on.  I'm trying to get *most* of what -xia does, but without
normal navigation being completely taken over; I don't really *want* the
user in Update mode on most, if any records -- they'll be scanning through
them and using @key routines to dispatch them.  I just want the @key routine
to be able to automagically move them to the next record down the index that 
was selected.

(And incidentally, that record pointer should be cached by dclerk *before*
the user goes into update mode; I have a pissy comment in some 1996 vintage
code that notes that you don't, and if I change the index field, all is
chaos; the comment actually mentions a line number, because the client had
4.1 sources on their machine cause they were an AT&T 3b2 port/beta site. :-)

Cheers,
-- jra
-- 
Jay R. Ashworth                  Baylink                       jra at baylink.com
Designer                     The Things I Think                       RFC 2100
Ashworth & Associates     http://baylink.pitas.com         2000 Land Rover DII
St Petersburg FL USA               #natog                      +1 727 647 1274