D
Dean Slindee
We have a networked Access 2003 application (.adp) with a SQL Server 2000
backend. Changes made by one user to a data row are not visible to another
user viewing the same row unless both users quit the application. I presume
this is some type of buffer situation, where both users get complete buffers
(copies) of the data(base) when they launch the application. And then when
the first user moves off the updated row, the second user's buffer is not
automatically updated.
Is my analysis close to correct? Is there any way to force or accomplish a
refresh of one or many user's buffers?
How does Access work internally regarding these buffers?
Thanks in advance,
Dean S
backend. Changes made by one user to a data row are not visible to another
user viewing the same row unless both users quit the application. I presume
this is some type of buffer situation, where both users get complete buffers
(copies) of the data(base) when they launch the application. And then when
the first user moves off the updated row, the second user's buffer is not
automatically updated.
Is my analysis close to correct? Is there any way to force or accomplish a
refresh of one or many user's buffers?
How does Access work internally regarding these buffers?
Thanks in advance,
Dean S