hi gurus
the scenario
Frontend - MS Access (not yet decided whether MDB or ADP)
Backend - MS SQL Server
it is a conversion from MS Access backend to MS SQL Server Backend.
Planning to create stored procedures for all the Inserts, Updates,
Deletes and Business Rules / Validations wherever it is possible.
the problem
i am running in concurrency problem. the same classic scenario of two
users retrieving the same row (record) from the same table. it allows
both the user to update the record, that is, the user who updates last
has his changes saved though he retrieved that particular record
second.
what i need is that the user who retrieved the record second shouldn't
be able to update or delete the record when it is already retrieved by
any other user.
would appreciate if someone pointed me in the right direction to solve
the above problem, i know it is related to isolation property but am
not sure
thanx in advance
regards
bala
FAQ
Search
Profile
Private Messages
Log in
