# Using same transaction during update

**URL:** https://talk.remobjects.com/t/using-same-transaction-during-update/17293
**Category:** Data Abstract
**Created:** [August 29, 2018, 10:31am UTC](https://talk.remobjects.com/t/using-same-transaction-during-update/17293 "2018-08-29T10:31:47Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![tobygroves](https://talk.remobjects.com/letter_avatar_proxy/v4/letter/t/3da27b/32.png) [@tobygroves](https://talk.remobjects.com/u/tobygroves)
#### Post date: [August 29, 2018, 10:49am UTC](https://talk.remobjects.com/t/using-same-transaction-during-update/17293/3 "2018-08-29T10:49:32Z")

</div>

I think I may have figured it out. The problem is that my code which is executing the command is creating a fresh service instance which has its own transaction.

What I need to do is make this service instance use the same transaction as the existing instance being used by the update process.

I did something very similar a while ago here: [Wrapping multiple client calls in a transaction](https://talk.remobjects.com/t/wrapping-multiple-client-calls-in-a-transaction/11119/20?u=tobygroves)

I have access to the service via the Sender.Service in the BeforeProcessChange handler so I should be able to pass this to my command execution code and make it use that. I’ll give it a go.

---

_[View the full topic](https://talk.remobjects.com/t/using-same-transaction-during-update/17293)._