>I have a fox stored proc. that does all updates to the tables: Inserts, Updates, Deletes. I send a string to that SP that is converted into a cusror. Then I scan that cusror and do updates. My question is do I need to lock a record which is about to be updated? Is transaction better way to hanlde multiple updates? Please, help.
>
>Thanks, Mark
I believe the trigger automatically goes within a transaction.
You can also use buffering and TableUpdate(), to make sure changes can be comitted.
Hilmar.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
