>Pulling even the top 200 records can take 1-3 minutes. Very slow. We're trying to see what the delay is (it could be anything in the topology other than the driver). They don't have SQLServer on their system so we can't test pulling records from sqlserver as a comparison. In the past, adding an index tag in foxpro on the tables has improved performance, but we really don't know what may be the culprit here.
>
>
>
>>Tracy,
>>
>>Hard to tell when we don't know the case of the behavior.
>>For instance, try to play with setting the recordset cursorlocation. This is what helped me in the past:
>>
>> .CursorLocation = adUseClient
>>
>>
>>
>>>Foxpro tables exist across a T1 link. Using a winform (for testing but it will be a process on the server) in vb.net and OLEDB to ADO to grab data from vfp tables. Very slow. Recommendations? The best way to handle it?

What is the size of the data your pulling down? Are you testing against a single or multiple tables and with no index?