Very Computer

I am having trouble with locate indexorder.
I am using
  LOCATE INDEXORDER NEXT PATTERN "a.."

When doing this command repeatedly in a script, sometimes
Paradox finds several of the fields with the data starting
with an 'a', sometimes it finds none. When Paradox thinks
that all the matching records have been found, it cycles
back to the first found record (but misses many records
that should have been found).

The actual number of records found this way seems to
depend on the table, so there must be some kind of,
should I say, pattern.

What am I doing wrong?

I have done a LOCATE INDEXORDER without the NEXT before
giving one with NEXT.

Timo

--
/--------------------------------------------------------------------------/

/ O Fortuna, velut luna, statu variabilis, semper crescis, aut decrescis ! /
/--------------------------------------------------------------------------/

Quote:>back to the first found record (but misses many records
>that should have been found).

>The actual number of records found this way seems to
>depend on the table, so there must be some kind of,
>should I say, pattern.

Repeated LOCATE INDEXORDER NEXT PATTERN "a.." stops on
the first uppercase 'A' it finds. After the first upper
case 'A' it cycles back to the first found record and
misses all the rest.

According to the manual, when using PATTERN case should
be ignored.

Seems to be a bug.

Timo

--
/--------------------------------------------------------------------------/

/ O Fortuna, velut luna, statu variabilis, semper crescis, aut decrescis ! /
/--------------------------------------------------------------------------/