BTW, you have to set FetchAsNeeded = .T.

Well, FetchSize can be problematic. It does limit you to the next nnn records from the start of the table. And if you traverse the cursor to a record outside of the nnn amount, you are going to be waiting a very long time...

I think you are best suited to SQL passthrough and very distinct queries -or- SQL passthrough and calls to stored proces that execute very distinct queries. If you can live without binding data directly to controls, you might want to start looking at using ADO to grab the data.


>thanks i keep reading all this horrible stuff about remote views and really i wouldnt even use them except i need to update and batch load data regularly from dbfs in our old system as well as for lookup screens and so of for later down the line the table that has the 11 million rows i need to see if a record is there and if so update it and if not delete it so i need to come up with a quick usefull solution if it wasnt soo much data i wouldnt be concerned or if the views worked similiar to linked tables in Access i wouldnt be worried i will try the fetch rows property does that limit you or does that just only pull a set a amount when you load up so that you can start sending updates and queries????