We have played only a little with Crystal and Fox tables. The major performance problem we came across was with filters on indexes in the table. We have a "not deleted()" filter and this killed the performance.
Since then I have heard that the workaround for this sort of problem in foxpro itself is to create an index on the same expression as the filter. We have not tried this yet.

HTH
Craig
>Do you have to use ODBC? Are you using a SQL command? Because Crystal will read DBF's directly through its own interpreter.
>
>JR
>
>>I have a connect to pass through ODBC with Dbc for Crystal Report
>>but It's very, very .... slow
>>Somebody know Why?