Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 1 to 10 of 11 total |
Record is in use by another user |
Thu, Feb 11 2021 7:44 AM | Permanent Link |
Kees Lagendijk | I seem to get the above mentioned more and more. Can anyone help me out?
Gr, Kees |
Fri, Feb 12 2021 1:14 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Kees
A number of questions - are the records genuinely locked? - are you using f/s or c/s? - are you using optimistic or pessimistic locking? Roy Lambert |
Sat, Feb 13 2021 4:17 PM | Permanent Link |
Kees Lagendijk | Roy Lambert wrote:
Kees A number of questions - are the records genuinely locked? - are you using f/s or c/s? - are you using optimistic or pessimistic locking? Roy Lambert It occurs when a user tries to open a record. It most cases cannot be locked, because there is no other user. F/S or C/S makes no difference. I am using pessimistic locking. Kees Lagendijk |
Sun, Feb 14 2021 1:50 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Kees
Another question - what error message do you get when the problem happens? OK wild guessing and suggestions time: 1. If no other user try optimistic locking (I'd be willing to make a small wager it won't work) 2. If you're running across a LAN there are hardware issues 3. The table(s) are corrupted - try repairing them 4. Delete the dbisam.lck file Roy Lambert |
Sun, Feb 14 2021 10:28 AM | Permanent Link |
Kees Lagendijk | Roy Lambert wrote:
Kees Another question - what error message do you get when the problem happens? OK wild guessing and suggestions time: 1. If no other user try optimistic locking (I'd be willing to make a small wager it won't work) 2. If you're running across a LAN there are hardware issues 3. The table(s) are corrupted - try repairing them 4. Delete the dbisam.lck file Roy Lambert --------------------------------- Roy, the message is "record has been changed or is in use by an other user". Not really an exception but more a warning? The opt locking I will try. Happens also to users in stand-alone setting. Tbables repaired - did not make a difference. But, what do you mean by deleting the lockfile? when should I delete that file? Any time it occurs? Kees.3 |
Sun, Feb 14 2021 10:54 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Kees
>But, what do you mean by deleting the lockfile? when should I delete that file? Any time it occurs? No - thinking about it - just rename the file (say to OLDdbisam.lck) at least that way if things keep on happening you can send Tim both the old and new lck file so he can have a look if locks are being left behind (I don't remember it but it might happen).. You should never need to delete it since it should be cleared out when the user closes the application. Roy |
Mon, Feb 15 2021 11:37 AM | Permanent Link |
Raul Team Elevate | On 2/14/2021 10:28 AM, Kees Lagendijk wrote:
> the message is "record has been changed or is in use by an other user". Not really an exception but more a warning? > The opt locking I will try. Happens also to users in stand-alone setting. Tbables repaired - did not make a difference. > But, what do you mean by deleting the lockfile? when should I delete that file? Any time it occurs? Are you 100% certain nothing else is modifying those records ? For example sql exec command that is run after user opened the table or some background process that updates record(s) or such ? Raul |
Mon, Feb 15 2021 12:20 PM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Raul
That prompts me to wonder if a transaction is in use. Roy Lambert |
Mon, Feb 15 2021 7:29 PM | Permanent Link |
Raul Team Elevate | On 2/15/2021 12:20 PM, Roy Lambert wrote:
> That prompts me to wonder if a transaction is in use. Roy, Possible but I would expect a different error for those. This one I assume is the error 8708 and "Record has been changed or deleted by another user, session, or table cursor in the table X" one. This one can be common when posting changes in multi user setups (especially if daataset has not been refresh for a while). General fix is to cancel post, refresh recordset, reapply changes and post again. What i find curious is OP said this is happening when opening a record (!?) - so either it's deleted record or it's actually during post - and that it's a single user setup (either another session in app is changing something or sql execution or such). Anyways - more info needed Raul |
Tue, Feb 16 2021 12:50 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Raul
It could even be something that has little direct connection with the table. I had to try and sort something like this yesterday using ElevateDB. It involved three of my homebrew components - subclassed dbgrid & table and a self written distractor (ticking clock style). The distractor uses the dbgrid's canvas to display. The sequence went start distractor, run an EMPTY TABLE query, stop distractor. I got the ElevateDB equivalent of "Record has been changed or deleted by another user, session, or table cursor in the table X" every so often. Roy Lambert |
Page 1 of 2 | Next Page » | |
Jump to Page: 1 2 |
This web page was last updated on Tuesday, September 17, 2024 at 04:19 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |