I found what the problem was! I discovered that my SP/Trigger code for
"before delete" worked perfectly fine when deleting a row from the data browser
at an R> prompt, but failed when run from within an edit form for that
table. That gave me a "blues clue" for sure!
My form had a Delete button with a pre-defined "delete row" action. This
apparently caused the "invalid cursor state" when the trigger tried to
evaluate. I changed it so that the Delete button did this:
SET VAR vDeleted TEXT = 'YES'
RESETROW
CLOSEWINDOW
RETURN
And on the calling form, it checked the value of the vDeleted variable and
did a "delete row" from there. Now the trigger works great!
Karen
