During the 6 hour run, did the client happen to notice the bottleneck? Was it CPU-bound, local disk, network, remote server, ... ?

>Well that's the thing. I'm running SQL squeries that should be returning one row at a time.
>
>The client gave me a table with 6000 rows. The production table has 600,000 rows, so I need to mock up the data and check it out.
>
>But that got me thinking that if I could use the index and do a seek, it would be a lot faster.
>
>
>
>>I've done quite a bit work with VFP tables with .NET.
>>I run the VFP queries first from the VFP command window to get an idea of the performance I'll get and to see whether there is any Rushmore optimization.
>>You'll get roughly the same performance with the same query with OLEDB.
>>
>>
>>>That's what I'm doing now.
>>>
>>>The app reads PDF's full of invoice payment information into into VFP tables. It looks up the invoice in one table, then writes the payment data to other VFP tables.
>>>
>>>The client reported that the application took 6 hours to complete, so I need to find a way to speed it up.
>>>
>>>
>>>
>>>>You won't do it that way. You'll use the VFP OLEDB provider and do everything through SQL statements
>>>>
>>>>>I have a C# WPF application that needs to read/write from VFP tables.
>>>>>
>>>>>What's the syntax for setting an index and doing a SEEK from within C#?
>>>>>
>>>>>Thanks