browse lookup and -v processing

[John Esak]

> Kenneth Brody wrote:
> > Quoting John Esak (Sun, 30 Jul 2006 23:47:51 -0400):
> > [...]
> >
> >>There is a much better way than -xa. I've put it up here a couple times.
> >>Do:
> >>
> >>    .../rclerk filename -s0   (or any existing screen)
> >>
> >>Then do everything in @once, when you're done, EXIT.  No need to clean
> >>up the -xa. Even works with a file that has NO records in it.
> >
> I just wanted to add a note here that might save people some problems.
> I do this in @done and using a selection set entered @rn lt 0.  Big
> mistake.  On the Windows system, this caused an extreme lock up/crash.
> I usually do @rn lt 1, which never selects any records, but I figured
> @rn lt 0 would do the same thing, but I was really wrong.
>
> So if you want to use @done or @once, be sure you make a selection set
> that will never select any live records.  Also make sure the top of the
> table starts with END so in case you do select records nothing happens
> except it uses up time.
>
> Nancy

I'm not sure what you are saying here. I don't need to care about what
records are selected when I use @once for gathering info form the user and
then running a system report. That is because when the @once processingis
finished... I execute an EXIT.  Are you saying you can demonstrate some
problem with this?  I mean even if you had a selection set that grabbed 10
records or one record (or no recrods... which is not really required because
@once is not "yet" at a record anyway) what could go wrong?  When the EXIT
happens *cler exits.  Do yu see something diferent with @once???

John