OK, just to answer my own question, it's not really a solution, but you should be able to work around this by putting the whole transaction into a stored procedure on your SQL Server and calling that from Tango.
Ed ----- Original Message ----- From: "Ed Edgar" <[EMAIL 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 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 transaction. Horrible thing to do in a production environment, I know, but for the moment I'm stuck with it... Anyone got an actual solution? Ed Edgar The Princeton Review International Hosting, Tokyo [EMAIL PROTECTED] http://www.review.co.jp http://www.princetonreviewhk.com http://www.tprthai.com http://www.princetonreview.com.tw ----- Original Message ----- From: "Dan" <[EMAIL PROTECTED]> To: "Multiple recipients of list witango-talk" <[EMAIL PROTECTED]> Sent: 2002?9?12? 18:25 Subject: Witango-Talk: Transaction riddle... | This problem drives me crazy... | | It took my college and I ages to figure what happening: | | After developing a witango application on a developing machine on which | everything works fine, we moved the whole thing to our server - Win 2000 / | MS SQL. We're using the developing version on the first (developing) | machine, the Witago server on the other. | All seems to work but on every action than uses Begin Transaction ... End | Transaction Witago Service crashes. The logs shows that the service | unexpectedly terminated. The service is being restarted, but database | connectivity doesn't work anymore... until the service is manually stopped | and restarted again. When removing the transaction code things work as | expected. Of course, leaving the transaction out in a production environment | is unacceptable. Anyone with similar experience or maybe even a solution? | | Dan | | ________________________________________________________________________ | TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] | with unsubscribe witango-talk in the message body ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
