Chris,

You do not need to "bring the table into the project" or the .DBC to add an index. FPW (and previous) tables have been benefitting from Rushmore optimization for years.

100,000 records is not large at all for FoxPro.

Please post the exact syntax of your query and the exact syntax of your index tags so we can help. The values in the WHERE clause must exactly match the values in the indexes. It sounds like you need an index on EmployeeId and one on PayDate.

To test the benefit of the tags, without the variable of network speed, copy the table to your hard drive and test there. If you have space problems use only the necessary fields in your test table.

Also, you may or may not benefit from a tag on DELETED() if you are running with DELETED ON. You should probably not have this index tag.



>I have an application that has to access a large table of employee pay data in order to perform a calculation. The table sits unindexed and external - each query of it is taking over a minute which the users think is a drag.
>
>
>The table has about 100K records. The record looks like
>
>
>pay period (date)
>employee id (integer)
>paydate (date)
>other numeric pay values
>
>
>the logic of the query selects records for an individual employee (by id number) after a specific date. Employees have a record for each pay so there are multible records for each employee id in the file.
>
>I had thought about bringing the table into the project and setting up an index on employee id to help the query but the improvement was zero.
>
>Can anyone suggest a strategy?
>
>
>TIA
>Chris