![]() | ![]() Products ![]() ![]() ![]() ![]() |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 1 to 3 of 3 total |
![]() |
Wed, Jun 24 2009 7:59 PM | Permanent Link |
"Al Vas" | Hi,
We have a client who is often getting a 'Cannot unlock table or record in table Booking' message. What does this exactly mean? We are using pessimistic locking, so when a user edits and entry another user cannot edit it. But the message would in this case be something like 'record is being used by another user.'. Under what circumstance(s) would a user session not be able to unlock a table or a record? It appears in line with this (although I cant be certain) that these sort of messages are followed by '8708 Record has been changed or delted by another user' messages presumably when another user is trying to access and edit the same record. On another historical note we only seem to have started getting this error when we changed the source code of DBISAM to fix another issue as identified in the following link: http://www.elevatesoft.com/newsgrp?action=searchopenmsg&group=5&msg=61001&keywords=8709*#msg61001 relating to '#8709 No current record in table xx' errors. We are using DBISAM V3.30 Help appreciated. Regards Alex |
Thu, Jun 25 2009 9:00 PM | Permanent Link |
"Al Vas" | Hmm, no ideas, anyone?
Alex "Al Vas" <noreply@noreply.com> wrote in message news:037F6DDA-6A12-48A3-98D0-07FA6CFCF1BD@news.elevatesoft.com... > Hi, > > We have a client who is often getting a 'Cannot unlock table or record in > table Booking' message. What does this exactly mean? We are using > pessimistic locking, so when a user edits and entry another user cannot > edit it. But the message would in this case be something like 'record is > being used by another user.'. Under what circumstance(s) would a user > session not be able to unlock a table or a record? > > It appears in line with this (although I cant be certain) that these sort > of messages are followed by '8708 Record has been changed or delted by > another user' messages presumably when another user is trying to access > and edit the same record. > > On another historical note we only seem to have started getting this error > when we changed the source code of DBISAM to fix another issue as > identified in the following link: > > http://www.elevatesoft.com/newsgrp?action=searchopenmsg&group=5&msg=61001&keywords=8709*#msg61001 > > relating to '#8709 No current record in table xx' errors. > > We are using DBISAM V3.30 > > Help appreciated. > > Regards > > Alex |
Fri, Jun 26 2009 11:58 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. ![]() | Alex,
<< Hmm, no ideas, anyone? >> Sorry, I skipped over this message yesterday. This type of issue was traditionally caused by issues with current record pointer changing after locking a record, thus causing the unlock to fail, and were related to issues with certain grids. However, it is also possible that there is a situation whereby 3.30 can experience this problem without such a grid issue, but I do not know what that might be at this time. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Wednesday, August 14, 2024 at 03:12 PM | Privacy Policy![]() © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? ![]() |