RE: fetch last error

You have attempted to acquire more locks than OnLine has been configured to hold. What isolation level are you using? If it's repeatable read then I wouldn't be at all surprised that this is happening: every row that gets touched on its way to find which is the last one of the million, has a lock placed (and left) on it. The obvious (not best) solution would be to lower your isolation level. Or configure more locks. Neither of which I would advise. The preferable solution would be to find some more efficient way of locating the row you want than having trawl through a million (unwanted) rows to get to it; you'd also do wonders for your response times. Surely you could get straight to the row you want through an index, perhaps with a SELECT MAX(col) or something similar. akent@cix.compulink.co.uk (Andy Kent) ------------------------------------- 44 272 742815