Xavier,

You probably don't need a new ODBC driver for SQL Server 7 as long as you aren't using any new SQL 7 features (like larger char and varchar fields). It's still probably a good idea to have your client install the latest drivers.

>Hi Josh,
>
>I have done what you suggested and will try at the client.
>I am running with SQL 6.5 and do not seems to have the problem, but it is when I go to the client running on SQL 7.0 that the problem seems to occur.
>
>Do I need a new ODBC driver for SQL 7.0 ?
>
>I will send my new version tonigh and we will see !!
>
>In any case many thanks for your support
>
>Xavier
>
>>Xavier,
>>
>>I'm not sure what's going on here. I would try setting the buffering to 5. Then, after you delete all the records do a TABLEUPDATE() (make sure that TABLEUPDATE() returns .T., otherwise an error was encountered). Then insert all the new records and do another TABLEUPDATE().
>>
>>>Hi Josh,
>>>
>>>I appreciate your support, I have set all my views to share connection and fetchsize to -1. I do not get the connection busy anymore but I get UPDATE CONFLICT from time to time using the same data so the data are valid.
>>>
>>>The program execustes as follow
>>>Select the view
>>>Delete all record
>>>insert all record from an other table
>>>
>>>It seems to me that the delete does not complete its task or can not event start it from time to time.
>>>
>>>When I select the view is there any chance for the program to start the delete before all records are retreived ?
>>>
>>>Should I set the views buffering to 5 rather than 3 ?