for blocks/statements can use multiple indexes brackets
to find records
which is not only faster but in some situations
a single index bracket will not include all the desired records
and would require a whole table to be scanned
e.g.
for each customer
where custnum <= 10 and name = "mary":
end.
if only one index would be used as was the case in v6
it would require a whole table scan
find can only use one index bracket
so following find prev/next can use the specified index cursor
to move backwards and forwards
and isn't possible if there are multiple indexes
unless a result-list is used, which isn't supported for find
which has alot to do with the way program were written back in v6
for example v6 browsers
the query object is intended to replace the find
in most cases, sometimes it's still simpler to use find
but why here it from me, you can read about it from da'man gus
technical articles \ the engine crew monographs @peg.com
i'd also recommend subscribing to the peg email group
sorry i sold out guys
it is expected behaviour if there is a week scope
e.g. repeat, for each etc.
and progress finds another reference to the buffer outside the scope
to raise the scope to include it
e.g.
for first customer:
end.
display customer with 2 columns.
the buffers scope is raised to include the display statement
you can force a strong scope using do for
you can read up about it in your e-docs
programming handbook \ record buffers and scope