We are working with a legacy MSSQL database and VB.NET. The following was determined by looking at the database directly after the page cycle finished.

psuedo code:

LoadOrCreate(ByVal val As Integer) As Obj
    Dim objID As Integer
    Using transaction = Session.Demand().OpenTransaction(TransactionOpenMode.New)
        Dim newObj As Obj = Obj.Create()
        With newObj
            .Prop1 = val
            .Prop2 = GetCalculatedPropValue()
        End With
        objID = newObj.ID
        If Not newObj.HasDuplicate()
            transaction.Complete()
        Else
            objID = newObj.GetDuplicateID()
        End If
    End Using
    Return Load(objID)
End Function

This gets called one or more times. It always works the first time it is called. It also works every time that is not the last time it is called. The Prop# properties are not getting saved to the database the last time the above is called when it has been called at least once before. The object is always created if it was supposed to be. E.g.

Dim obj1 As Obj = Obj.LoadOrCreate(1) ' works '

AND

Dim obj1 As Obj = Obj.LoadOrCreate(1) ' works '
Dim obj2 As Obj = Obj.LoadOrCreate(2) ' fails '

AND

Dim obj1 As Obj = Obj.LoadOrCreate(1) ' works '
Dim obj2 As Obj = Obj.LoadOrCreate(2) ' works '
Dim obj3 As Obj = Obj.LoadOrCreate(3) ' fails '

At the end of the button OnClick subroutine, the user is sent to a success page using Response.Redirect(). My hunch is that the Prop1 value is not getting saved to the database because the transaction opened by DataObject at the beginning of the page request is never successfully closed/completed, and the values are getting written in other cases because there are a number of database read and write operations that would trigger database visits by DataObjects in other circumstances. Does anyone know how to force DataObjects to make a database visit (i.e. write pending changes) or have alternative ideas as to why the Prop values are not getting saved in this one case?