Support Forums - View Thread

View Thread

The following is the text of the current message along with any replies.

Messages 1 to 5 of 5 total

ElevateDB Error #1006 Cannot unlock the row in the table ...

Mon, Dec 27 2010 10:45 AM	Permanent Link
Michiel ENK Software	Hi, I have a couple of tables with constraints on them. When I try to delete a specific record (I get the expected PK constraint error) then I try to change the same record into someting else (I get another expected constraint error), but after that I also get the Error #1006 Cannot ... Howcome?
Mon, Dec 27 2010 11:33 AM	Permanent Link
Michiel ENK Software	Michiel wrote: Hi, I have a couple of tables with constraints on them. When I try to delete a specific record (I get the expected constraint error) then I try to change the same record into someting else (I get another expected constraint error), but after that I also get the Error #1006 Cannot ... Howcome?
Wed, Dec 29 2010 7:16 AM	Permanent Link
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com	Michiel, << I have a couple of tables with constraints on them. When I try to delete a specific record (I get the expected PK constraint error) then I try to change the same record into someting else (I get another expected constraint error), but after that I also get the Error #1006 Cannot ... >> I can't reproduce this with 2.04 Build 4. What version of ElevateDB are you using ? Also, can you send me your database catalog, or the DDL for the involved tables ? -- Tim Young Elevate Software www.elevatesoft.com
Mon, Jan 3 2011 6:01 AM	Permanent Link
Michiel ENK Software	"Tim Young [Elevate Software]" wrote: I can't reproduce this with 2.04 Build 4. What version of ElevateDB are you using ? Also, can you send me your database catalog, or the DDL for the involved tables ? Hi Tim, Sorry for my late response. I was using version 2.03 Build 13. After updating to the lastest version the problem seems to be solved. I dont know if the problem is now gone because of the update or because of some other reason, but the problem is now solved. Thanks for your reply and help.
Tue, Jan 4 2011 5:59 AM	Permanent Link
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com	Michiel, << Sorry for my late response. I was using version 2.03 Build 13. After updating to the lastest version the problem seems to be solved. I dont know if the problem is now gone because of the update or because of some other reason, but the problem is now solved. >> Thanks for the update. I'm glad that you were able to resolve the issue. -- Tim Young Elevate Software www.elevatesoft.com