ADP and SQL data concurrency

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

One of my developers tells me when using an Access ADP against a SQL Server
2000 back in there are concurrency issues. He has seen one user edit a
record while another user has the same record open and then the second user
can make changes and save the record without receiving any "the data has
changed" prompts.

Any ideas here?
 
I've never heard of this issue.. and i've tested for it before.

does your table have a timestamp column? I would try the same thing
with a table with a timestamp column and see if that helps.

I personally think that ADP is the best solution anywhere.

It's possible-- using ASP -- Yes--- Active Server Pages-- to have the
same symptoms.

I mean-- it's good that you test for this sort of thing. I just think
that these issues are easy to manage in an ADP.

-Aaron
 
Hello Jerry,
You wrote in conference microsoft.public.access.adp.sqlserver on Mon, 7 Aug
2006 12:02:19 -0700:

JB> One of my developers tells me when using an Access ADP against a SQL
JB> Server 2000 back in there are concurrency issues. He has seen one user
JB> edit a record while another user has the same record open and then the
JB> second user can make changes and save the record without receiving any
JB> "the data has changed" prompts.

JB> Any ideas here?

Yes, it would work exactly like this. However, when the first user also
tries to save the record, he would receive the warning that the record was
already changed by someone else while he was working with it.

Access is using client-side cursors, so no locking occurs in the database
when the record is opened for edit. Whoever saves first, wins.

Server-side cursors and proper locking become an artifact of the past, and
not only in Access. All new database methods in newer languages like vb.net
are explicitly webserver-oriented, they all are using client-side cursors,
effectively looking at the database as a big excel table.

Vadim Rapp
 
I just don't understand this.

the only place that i've ever had unexplainable locking problems??

is in MDB.

I have been called into a production line to troubleshoot MDB locking
problems at 2am more often then I'd like to admit.

I've never had ANY such problems with ADP. Frequently I use a sproc to
udpate records though; and if the data has already changed then I
forbid the change.. or something along those lines.

What it really comes down to is that ADP supports real locking and MDB
doesn't.

I totally disagree with your findings. I've never had any problems
with ADP locking-- maybe that's the point.

I just think that ADP is vastly superior to MDB for a bunch of
reasons... and a lot of them are specifically what you're talking
about.

-Aaron
 
Back
Top