Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
idontgetit
Starting Member
2 Posts |
 Posted - 2008-10-07 : 10:18:34
|
| I recently converted an access database to a sql server 2000 database and created an adp front end. I used the basic form creation to create a form that is associated to a single table. I've added in a timestamp field to keep things clean on the sql end, but now if someone edits a record at the same time as someone else, the only options I have are to abandon or overwrite instead of the record level locking that ms access used to provide. I have not implemented the form using an ADO and I am reluctant to do so. Is there any other way to implement pessimistic record level locking so users can not edit a record while someone else is editing it, while still being able to view other records? If this is not feasible/easy without and ADO. How would I go about acomplishing this using and ADO? |
|
|
idontgetit
Starting Member
2 Posts |
Posted - 2008-10-07 : 12:59:21
|
| I'm still having trouble finding a solution for this. Does anyone need any clarification on the issue or have any ideas where I could get some help on it? |
 |
|
|
|
|
|
adp sql record Level Locking