Then it is very likely that in the "Find" button click procedure LOCATE is used and the option to seek by index is disabled or it can not find the appropriate index name. You have two options here:
- find the default code for Find Button and modify as needed or;
- write your own procedure in the find.click.


>Sorry for taking too long to get back to you. I was still concentrating on other problems that have now been solved. Back to my problem:
>
>To search, we are using the find button created from the wizbtns class among the other navigation buttons. The field by which we are searching is a regular index and I have also tried destroying and rebuilding the index to no avail. I did not wipe out the cdx file. I only stripped off the index, saved changes, went back and recreated them. Is this enough? For saving, we are using the save button from the same set.
>
>There are no filters in the whole environment.
>
>Awaiting your feedback.
>>Just some thoughts. Let us start with "search".
>>1. "Reindex", it should be done from scratch. Remove index file and recreate it.
>>2. How do you perform "search"? Is it seek(), seek ..., or indexseek()? Does it depend on the method of searching?
>>
>>
>>>SOS Folkes!
>>>
>>>I have a multiuser system that is becoming too slow on searches and saving. The database is setup with code implied relationships. However, this is not the problem because, for example, there is a simple screen that looks only at one table that has around 52,000 records. It takes about two minutes to search and another three to save!!! I have tried packing, reindexing... to no avail. ANY IDEAS?