For the last few days they haven't had this problem. I'll collect the error logs and analyze them later this week when I update the program on users computers to see if I can track down the computer causing
the problem. What devex components are known to cause such problem? I'm using the latest versions of QuantumGrid 5 and related db editors. The program was built using the version released before the
most recent one.
Regards,

Garik

Garik,

<< What devex components are known to cause such problem? I'm using the
latest versions of QuantumGrid 5 and related db editors. The program was
built using the version released before the most recent one. >>

Frankly, they release so often that it's hard to keep track of what versions
have had issues with DBISAM and vice-versa.  We usually try to work around
the issues inside of DBISAM, but sometimes they get re-broken when they make
changes again.  The biggest issues with record unlock issues have been with
the QuantumGrid product.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim


When you have a few moments can you let me know what type of thing could cause it and I'll have yet another wade through the appropriate bit of code in my app.


Roy Lambert

Roy,

<< When you have a few moments can you let me know what type of thing
could cause it and I'll have yet another wade through the appropriate bit of
code in my app. >>

In relation to DevEx, or in general ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim


General cos I don't use DevEx

Roy Lambert

Roy,

<< General cos I don't use DevEx >>

In general, this normally only occurs with re-entrancy when an action is
taken that isn't expected by the engine and the state of a given record
buffer is messed up.  In such a case, DBISAM ends up trying to unlock the
wrong record and the error appears.

--
Tim Young
Elevate Software
www.elevatesoft.com