Hi
We are using Devforce 5.1.
We have a scenario where we have a table of the following structure:
TaskName <== Primary Key
Description
... + some other fields
If I delete a Task Entity with say (TaskName = 'Task1') by going myTask1.EntityAspect.Delete(), and I don't persist the change to the database (because I'm not ready to). If I then create a new Task with the same TaskName ('Task1') it gives me a duplicate entity error saying there is already a task with Task1, even though the original task is marked for deletion.
Why is this so? and how do I get around this problem.
Thanks
Jacob Jozwiak