Hi Ian Boys (Bozz) / Hi all Clipper experts,
The exhaustive testing reveals that it is still failing in some cases. Apart from getting duplicate serial numbers, it is also not able to keep all the indexes updated, resulting it to allow duplicate document numbers. Do you have any other...
Hi Ian Boys (Bozz),
By implementing COMMIT statement after repl or delete during rock() and just before unlock and with the steps given by your suggested link www.jsiinc.com, my problem of rlock() failure is resolved. During primary testing the problem of getting same serial number by two...
If novell based multiuser application is used as it is on Windows 2000 or NT, record lock fails and nodes receive old information from the record, while it is under lock for updation from one user. Statement "Commit" should be inserted immediately after any updation or deletion before unlocking...
Hi Ian Boys,
DTE Systems Ltd.
Thanks for your help providing the link from www.jsiinc.com, but after trying all the registry changes recommened there, also we continue to face the same problem of getting same serial number for two terminals. We tested the solution today itself, and is failing...
Yes, Even we have faced this problem of getting same sequence number again and again by different terminals. We are using rlock() just before update, and updating record if rlock() is successful. The same software is working fine with Novell netware, but gives this problem, when attempted on...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.