>>Peter,
>>
>>Are you updating the view or requerying it? If you're requerying the view is the view parameterized or does it return all 36,000 records? If that's the case then that explains the 7 seconds. When you requery a view all of its records are copied from the base table to your view. You may be able to speed things up by setting the view's FetchSize to -1 (return all records at once). If that doesn't help you may want to consider changing the view to return a subset of the database.
>>
>>>I am accessing a standard table in a Foxpro DBC container through and ODBC connection. You mean that a 7 second requery of the view is ok?
>
>No, unfortunately in that case I need to bring all records at once, because calculations are based on records anywhere in the table. If that is a normal speed (7 secs.) I guess what I will do is use a control table to check if there have been any changes to the data since the last requery. Thanks for the help.
>
>Peter

The speed issue is based on reading 36,000 records through ODBC. This would be an issue no matter what back end you are using. Two things come to mind, you have a design issue or update issue if you REQUIRE all 36,000 records when updating.

There must be some 'reason' to determine which records are required for the calculations. You should have a method to bring in only those records that are required. An alternative is to have multiple views of the same table, all using different parameters and retrieving only the subset of records required.