Re: ISAM error: out of locks

In article <32B8F71A.6B7@netcomuk.co.uk>, Ian Goddard <igoddard@netcomuk.co.uk> writes >1. I agree with everything Clem says. > >2. If you are getting this problem when doing large updates with no >other users on the system you could use LOCK TABLE xxx IN EXCLUSIVE MODE >within your transaction. This will only use up one lock for the whole >table instead of a lock for each row affected. > >Ian Perfectly true unless you are using SE 5.01 or (I think) SE 5.00 in which case there is a bug which means that you *still* get a lock for each row processed rather than one for the whole table! If this is the case I suggest upgrading to SE5.07 or whatever is the latest version for your platform. > >Province wrote: >> >> I received the ISAM error "-134 No more locks" together with the -908 error >> for quite a long time now trying to access the UNIX server. -- Sally Woolrich