Re: Shared db update between VB.NET and VB6

Tech-Archive recommends: Fix windows errors by optimizing your registry

Oenone wrote:
> However, this means that I cannot put a single transaction around the
> updates performed by both the application and the plug-in (as each is
> a separate connection). If one should fail after the other has been
> committed, I have lots the integrity of my data.

I actually found the answer I was looking for in the end, but it turned out
to be a SQL Server problem rather than ADO.NET.

The solution is to use bound connections (sp_bindsession). This allows two
separate connections (one in ADO.NET and the other in ADO) to share the same
transaction. They will therefore not block one another, and all updates can
be committed in a single atomic operation.

--

(O) e n o n e


.

Relevant Pages

  • Re: Updates in a transaction
    ... you can do GetChanges on the dataset first to extract a new ... > within an single transaction. ... > the DataSet such that it knows the recent updates are still outstanding? ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Updates in a transaction
    ... Dick, Sahil is right... ... > within an single transaction. ... > the DataSet such that it knows the recent updates are still outstanding? ...
    (microsoft.public.dotnet.framework.adonet)
  • Updates in a transaction
    ... within an single transaction. ... If I rollback the transaction how do I reset ... the DataSet such that it knows the recent updates are still outstanding? ...
    (microsoft.public.dotnet.framework.adonet)