locked up users

nquest

I have users who lock each other aleast once a day. The enviroment is winows xp pro, windows 200 server standalone with Navision 3.10a


The implicit locks are typically caused by poor architecture, for example:


User A

---

User B ========================================= TableA.MODIFY

---

CONFIRM (something) ----

---

TableA.GET(

User B will get that locking problem, until the process at the user A will end, or a COMMIT is issued.

Please any way to resolve this issue ? via patch , update , etc

Thanks

bostjanl

nquest wrote:

I have users who lock each other aleast once a day. The enviroment is winows xp pro, windows 200 server standalone with Navision 3.10a


The implicit locks are typically caused by poor architecture, for example:


User A

---

User B ========================================= TableA.MODIFY

---

CONFIRM (something) ----

---

TableA.GET(

User B will get that locking problem, until the process at the user A will end, or a COMMIT is issued.

Please any way to resolve this issue ? via patch , update , etc

Thanks

Is this locking problem in original Navision code or in costumized code?

In coustumized code you should use COMMIT,..


bostjan

nquest

the locking error is problem in original Navision code any known answers?

Luc_VanDyck

What is the ID of the object where the problem is situated (codeunit, report)?

jae3240

This locking problem is a known issue in Attain 3.10!

The solution that I have received from our local Solution Center is to upgrade to Attain 3.6 version executables.

Contact your Solution center and they should be able to help you.

Hope this helps!

John