VBA, .mdb file & Record Level Locking (NOT!)

.mdb file & Record Level Locking (NOT!)

Author	Message
David Ree #1 / 3	.mdb file & Record Level Locking (NOT!) Hi Everyone - I am experiencing a problem with my .mdb file not locking at the record level. Let me give some brief background. I am working on a database in Acc97, and I need to have many users share this database. The problem is that it seems that we can have more than one user IN the database at a time, but there are weird conflicting errors regarding record locking. It is set to record-level locking...doesn't that mean that someone looking at a list of records shouldn't be able to view a record while it is "checked out"? And certainly not be able to make changes? And yet, my people can. Either that, or sometimes they can make changes, and it gives them a notice that the data has changed since they opened the record, and if they save their changes, the last persons changes will be lost. How do I solve this dilema? Right now, we often end up with users trying to use the database, and having to call around to find out who's in it, and ask them to please close it (when they are done), so they can have their turn. Also, if anyone has any other creative solutions to this problem, I'm all ears. :) Thanks! David Reed
Mon, 17 May 2004 22:11:04 GMT

Van T. Din #2 / 3	.mdb file & Record Level Locking (NOT!) Quote: > Hi Everyone - I am experiencing a problem with my .mdb > file not locking at the record level. Let me give some > brief background. I am working on a database in Acc97, > and I need to have many users share this database. The > problem is that it seems that we can have more than one > user IN the database at a time, but there are weird > conflicting errors regarding record locking. It is set to > record-level locking...doesn't that mean that someone > looking at a list of records shouldn't be able to view a > record while it is "checked out"? And certainly not be > able to make changes? And yet, my people can. Either > that, or sometimes they can make changes, and it gives > them a notice that the data has changed since they opened > the record, and if they save their changes, the last > persons changes will be lost. > How do I solve this dilema? Right now, we often end up > with users trying to use the database, and having to call > around to find out who's in it, and ask them to please > close it (when they are done), so they can have their turn. > Also, if anyone has any other creative solutions to this > problem, I'm all ears. :) > Thanks! > David Reed
Tue, 18 May 2004 08:54:41 GMT

Van T. Din #3 / 3	.mdb file & Record Level Locking (NOT!) (sorry for the empty response previously) You might have set the Default Record-locking in the Database Options but the RecordLocks Property of the Form may still have "No Locks" selected. Set both the Default Record-locking (in Options ... window) and the Form's RecordLocks Property to "Edited Record". BTW, even if the Record is locked, other users still can see the Record but they cannot edit the Record. Only the user who locks the Record can edit the Record. Note also that A97 actually locks a 2 KByte page which contains the relevant Record, not just the actual Record. HTH Van T. Dinh Quote: > Hi Everyone - I am experiencing a problem with my .mdb > file not locking at the record level. Let me give some > brief background. I am working on a database in Acc97, > and I need to have many users share this database. The > problem is that it seems that we can have more than one > user IN the database at a time, but there are weird > conflicting errors regarding record locking. It is set to > record-level locking...doesn't that mean that someone > looking at a list of records shouldn't be able to view a > record while it is "checked out"? And certainly not be > able to make changes? And yet, my people can. Either > that, or sometimes they can make changes, and it gives > them a notice that the data has changed since they opened > the record, and if they save their changes, the last > persons changes will be lost. > How do I solve this dilema? Right now, we often end up > with users trying to use the database, and having to call > around to find out who's in it, and ask them to please > close it (when they are done), so they can have their turn. > Also, if anyone has any other creative solutions to this > problem, I'm all ears. :) > Thanks! > David Reed
Tue, 18 May 2004 09:04:02 GMT

Page 1 of 1

[ 3 post ]