I tried the asynchronous option but things were still slow. After poking around in the indexes, I think that things on the Oracle side need to be improved. I am actually running queries on Views that have some UNIONS in them that may not have the right indexes available to run well

In any case, I'm probably going to need to have the Oracle DBA make some changes.

Thanks for all your help

David,

>
>Do you judge faster by when you first see a results set [in Access]? What I have noticed here is MS Access returns an initial results set and continues to retrieve in the background as needed [asynchronous]. You can do this in VFP also. You are probably using the Synchronous option. If you switch to asynchronous and set records to fetch at 100 or so, you will get a quicker turn around. You will get control of VFP returned back to you. In the Advanced Options under Query of the View Designer, you can also set the property to Fetch as Needed.
>
>If testing at the command window [or anywhere in code for that matter], do not issue any commands like Count, Sum, Reccount(), etc., otherwise you will sit-and-spin until all the records have been fetched.
>
>Usually, it is best to retrieve only a small set of data to work with using parameterized views. Then you can change the value[s] of the parameter[s] and issue a Requery() as often as is necessary.