I have an ADP w/ SQL 2000. Multiple users use the same form, a list-view of records. Because the ADP does not refresh data on a regular interval as an MDB does, if a user updates data in one record, the other users do not see that new data unless they manually click refresh. What I need is a way...
I do have some rather large updates. I am using optimistic locking. I have not tried changing the time out option through Access, but I had done so on the server with no results.
I do use alot of ADO recordsets, but I close/set them all to nothing when done with them. Since this is an ADP, all of the stored procedures and views are in SQL. There are alot of them as the database is quite large. There is no one sequence that triggers the error, a simple "Time Out Expired"...
I have an ADP/ADE file linked to SQL 2000 with about 10 users. As users log in and logout SQL does not release the users memory, and so the memory usage continues to grow until eventually SQL begins to give Time Out errors to the database users. Any idea why this might be happening or what I can...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.