any database experts here?

We were using MSACESS in our application before and our application used Multiple recordset from the same table. Recordset Refresh interval in MSACESS is 5 seconds. So we did not have problem with the multiple recordset getting other recordset changes.

Now we migrate to SQL server , we are opening recordsets as adDynamicSet and it is not reflecting the changes happening in the table. What is the default recordset refresh interval in sql server ado provider and is their any method to force the refresh in ADO. Anyone knows answer for this issue????/

try

rs.Open SQL,COnnection,adOpenDynamic, adLockOptimistic

Iouri Boutchkine
[email protected]

I tried to do some testing on this issue. My ADO recordset was updated automatically only when I used rs.CursorType = adOpenDynamic AND rs.CursorLocation = adUseServer. By automatic update I mean that changes made in one instance of my application were visible in another instance of the application. I used: TextBox + Microsoft ADO Data Control 6.0 + SQL Serever 2000 (Northwind database)

We use our recordset for a lookup search in 2 tables which hold so much data. This look up takes place in 33,000+time in each thread. Before that I used plain OLEDB interfaces and it worked fine. Now we are using ADO find method. If I open the recordset with serverside cursor as dynamicset, my SQL server getting hammered ( it is taking 50% of the cputime). But if i use clientcursor beformance is excellent only problem is the refresh. Everytime I cant open and close the table or make query in SQL server. I just want lookup as part of my recordset not in SQL server. Anyone knows any techniques, I dont understand why dynamicset not reflecting other user( process) changes regardless of the server or client side cursor. These dynamic recordsets need to be updated by the ADO provider, otherwise what is the difference from snapshot?.