If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Buffers/Concurrent Updates
This question concerns an Access .adp project with a SQL Server 2000
backend. If two users of the application bring up the same row in a table, the changes by the second user get saved whereas the first user's changes are overwritten (assuming the second user saved the row last). I presume that this is because both users have a full buffer of all the rows in the table. Is this presumption valid? Is there any practical way to refresh all of the user's buffers when a change has been made to the table? Like a requery? (The form uses the table for it's data source). Or are "real" Access programmers using some form of optimistic concurrency and timestamps. Thanks, Dean S |
Thread Tools | |
Display Modes | |
|
|