At 01:51 PM 05-09-01 +0200, you wrote:

>Hi
>Maybe I was not specific enough my sp works fine. It is because of the
>record that disappears that the dataset moans. I looked at the db code and
>it will raise an exception when the record where the cursor currently is, is
>not found. The only way I have found to circumvent this is by toggling the
>active property.
>Toggling active true and false works fine because the dataset is not to big,
>but if there is a better way I would like to use that rather.

Uh-huh, OK. :-) Call InvalidateBookMark on the dataset when you call the delete procedure; or change the dataset's RefreshAction to raInvalidateCursor . This tells IBO that it will have to check for that row's existence if it gets referred to again. Closing and opening the dataset is an EXTREEEEEEEME way to kill a cat. You are possibly getting this particular reaction from having something like CommitAction as caRefresh and RefreshAction as caKeepDataPos (can't say exactly except "I have been there". :-))

hth
Helen

All for Open and Open for All
InterBase Developer Initiative · http://www.interbase2000.org
_______________________________________________________