Subject Problem using locate
Author John Costanzo
I have an application that has a table with a little over 3 million
records. In the Paradox version the user can enter a record ID, which
is the unique primary key and select that record. The record is
selected instantly since the table uses ID as the primary key. In the
IBO version the locate goes off into never never land, puts out a
message that says Fetching Query Results - Row # xxxxxx and appears to
be searching the file sequentially. The table's primary key is the
ID. Can anyone tell me what I am doing wrong? The locate can take 15
or 20 minutes depending on the record ID selected.