Hello Dan,
I've come across this using MS SQL server before. It seems to be a problem
when you set the isolation level to "Read/Write Exclusive".
Anotherwards, WiTango tries to open the MS SQL table in exclusive mode,
leaving the table to only be opened by others in Read mode only. So, if the
WiT
setting the tango system variable
"transactionBlocking" to false solves our problem."
HTH,
Levin
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Ed Edgar
Sent: 12 September 2002 10:53
To: Multiple recipients of list witango-talk
Subject: Re: Witang
AIL PROTECTED]>
To: "Multiple recipients of list witango-talk" <[EMAIL PROTECTED]>
Sent: 2002?9?12? 18:52
Subject: Re: Witango-Talk: Transaction riddle...
Hi Dan.
I share your pain...
I had exactly the same thing happen on our Win2k / MSSQL PVSW Tango 2000 setup.
It looked like th
Hi Dan.
I share your pain...
I had exactly the same thing happen on our Win2k / MSSQL PVSW Tango 2000 setup.
It looked like the problem was triggered by an error a statement inside the
transaction block.
I fixed the error, and it appeared to work, but I decided to play it save and remove
the
