DCrake
Remembered
- Local time
- Today, 00:16
- Joined
- Jun 8, 2005
- Messages
- 8,626
Have you ever noticed getting a "You and another user have tried to update that record" error? Well, the common wisdom is that only one person can update one record at a time. However ...
Let's say you have fields A, B, C, D, E, and F and user 1 needs to update fields A, B, and C and user 2 needs to update fields D, E, and F. Well, if your recordset only includes the applicable fields and neither overlaps the other user, then EACH user can update the same record and not suffer from concurrency issues. This is a very neat development as it means that as long as you provide only the necessary fields to work with, users need not run into each other when it comes to different records.
This also applies to SQL Server as well as Microsoft Access.
Thanks to MVP Armen Stein for sharing this information.
Let's say you have fields A, B, C, D, E, and F and user 1 needs to update fields A, B, and C and user 2 needs to update fields D, E, and F. Well, if your recordset only includes the applicable fields and neither overlaps the other user, then EACH user can update the same record and not suffer from concurrency issues. This is a very neat development as it means that as long as you provide only the necessary fields to work with, users need not run into each other when it comes to different records.
This also applies to SQL Server as well as Microsoft Access.
Thanks to MVP Armen Stein for sharing this information.
