Roy Lambert wrote:

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.

-------------

We altered the locking to optimistic and the problems seems to have vanished. Fingers crossed...

Tx for thinking,
Kees