I seem to get  the above mentioned more and more. Can anyone help me out?

Gr,
Kees

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

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

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 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

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

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

Raul


That prompts me to wonder if  a transaction is in use.

Roy Lambert

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

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