DUH! You're right.

I just checked the demo app to see the behaviour there (just to make sure that this isn't one of those things that *I* screwed up) and it's the same.

If you cancel changes to a record that hasn't been committed, it's deleted from the buffer.

For today I'll leave it as it is. Won't have time to play with it until tomorrow, but I'll try to think of something in the meantime.

I really don't feel like adding a bizobj to the edit form. I love its simplicity. Hmmmm...

Alex


>Alex,
>
>When you launch the editform it is sharing the same dataenvironment as the original calling form. Hitting cancel will revert any and all changes. This could be considered a bug. Setting luRetval to .T. doesn't solve the problem because you would never be able to cancel any changes. Let me play with it for awhile and see what I come up with. You might try setting the edit form's datasession to private to see what happens, but you might have to create a new bizobj to implement this. Let's work on it and find out.