next number locked

sometimes our users met this error message :
"JDB9909103 - Fetch failed because the requested row of Next Numbers -
Automatic table is locked by another user."
when met this error , we delete the F40nn table and use P40nn to regenerate it.but i don't think this is a good way for solve the problem .
i want to ask,what caused this problem? what can we do to prevent it from happen?
thanks in advance.


B7332 SP12
AS400 V5R1
NT4

Why not call respond line 021-62492708.
regards,
yang da yong
----- Original Message -----
From: "bee" <[email protected]>
To: <[email protected]>
Sent: Friday, February 01, 2002 3:52 PM
Subject: next number locked


regenerate it.but i don't think this is a good way for solve the problem .
happen?
http://www.jdelist.com/cgi-bin/wwwthreads/showflat.pl?Cat=&Board=OW&Number=2
7914

Bee,

We had this problem also. We had to load the latest version of Client
Access. Our problem was that the row was locked by developers that had Fat
Clients and the record with the serk NN was the locked record.

Also, changing the 'lazy close' would solve our issue if you don't mind
the performance hit.

Tom

Xe Update 2, SP 17.1D1, ES AS/400, CO on SQL 7, Two instances
English/Western European and Japanese



OW 7332 SP 11.3VER, NT 4.0 SP 5, TSE 4.0 SP 4, Metrframe 1.8, CO SQL 7.0

hi,tom,
what do developer mean?are they the product users(end user) or the programmer?
if it mean program developer,then if developer close their fat client,the problem will disappear,is that right?

regards.
bee

B7332 SP12
AS400 V5R1
NT4

Bee,


In our case they are users with fat client that happen to develop OW
programs.

right?

Yes, the locks are released. This only appears to happen if the developers
do something (don't know what) in OMW.

Tom

Xe Update 2, SP 17.1D, ES: AS/400 CO: SQL 7 TSE: NT 4.0 Metaframe 1.8a




OW 7332 SP 11.3VER, NT 4.0 SP 5, TSE 4.0 SP 4, Metrframe 1.8, CO SQL 7.0