Change scope?

CHANGE is almost identical to BROWSE in what it can do. I just noticed
however that CHANGE has a <scope> which is rather odd for a browse like
command. Even more odd is how it works.. If I issue

CHANGE NEXT 3

on a table with some records then I can actually change up to 3 records
either "up" or "down" from my current position. As soon as I cross the 3rd
record boundary the window closes. This is the case if I move "up, up" or
"down, down" or even "down, up" etc. If I use the Record->Goto menu option
then in fact I can go to any record I like any number of times and edit data
provided I don't cross the record boundaries and the window will stay open.

What is the meaning of <scope> in the context of CHANGE?

Gene, is this good enough for your list of nasty questions?

--
regards
Andrew Howell

Neil
Tue Mar 21 19:07:14 CST 2006

BROWSE NEXT 3 works too. It isn't documented, doesn't error, and has no
concept of 3. Guess it's a backward compatibility thing from days long gone.

cheers,
Neil

> CHANGE is almost identical to BROWSE in what it can do. I just noticed
> however that CHANGE has a <scope> which is rather odd for a browse like
> command. Even more odd is how it works.. If I issue
>
> CHANGE NEXT 3
>
> on a table with some records then I can actually change up to 3 records
> either "up" or "down" from my current position. As soon as I cross the 3rd
> record boundary the window closes. This is the case if I move "up, up" or
> "down, down" or even "down, up" etc. If I use the Record->Goto menu option
> then in fact I can go to any record I like any number of times and edit
> data provided I don't cross the record boundaries and the window will stay
> open.
>
> What is the meaning of <scope> in the context of CHANGE?
>
> Gene, is this good enough for your list of nasty questions?
>
> --
> regards
> Andrew Howell
>

Gene
Fri Mar 24 18:47:41 CST 2006

On Tue, 21 Mar 2006 16:08:28 -0000, "Andrew Howell" <ajh@work> wrote:

>CHANGE is almost identical to BROWSE in what it can do. I just noticed
>however that CHANGE has a <scope> which is rather odd for a browse like
>command. Even more odd is how it works.. If I issue
>
>CHANGE NEXT 3
>
>on a table with some records then I can actually change up to 3 records
>either "up" or "down" from my current position. As soon as I cross the 3rd
>record boundary the window closes. This is the case if I move "up, up" or
>"down, down" or even "down, up" etc. If I use the Record->Goto menu option
>then in fact I can go to any record I like any number of times and edit data
>provided I don't cross the record boundaries and the window will stay open.
>
>What is the meaning of <scope> in the context of CHANGE?
>
>Gene, is this good enough for your list of nasty questions?

No. My questions are not technical questions but questions that
invite a wrong answer with a seemingly correct answer.

Picky technical questions are not supported.<G>

Sincerely,

Gene Wirchenko