Re: Delete Cursor: What To Use In Select Clause?

In those old days when referential integrity constraints didn't exist in order to enforce referential integrity you had to code it manually.So before actually deleting a record you wanted to check if it is allowed to do this and you wanted to prevent other users from concurrently check the same things for performance reasons. So you placed a lock on the record through an update cursor which said to anyone else "I am now going to do the delete", checked your referential integrity constraints and then did the delete.Of course with the newer versions you don't have to do it this way but I remembered that I have coded like this. Since the poster didn't provide any information about his Engine or what his application intended to do I thought that this could be a reason for coding like the way he did.As it turned out his case was a different one. It was my fault causing this misunderstanding that I didn't explain in detail what I meant. I hope this message has clarified my thoughts ... Regards Tolis +---------------------------------------------------------------------+ | V+K Relational Solutions email: tvarnas@compulink.gr | | Deligiorgi 26 tvarnas@orbit.de | | 546 42 Thessaloniki Voice: (30) 31 820270 | | Greece Fax: (30) 31 865463 | +---------------------------------------------------------------------+