From: toni.alfirevic@gmail.com   
      
   Hi,   
      
   has anyone ever encountered a problem with MSSQL that would manifest like   
   this.   
      
   If you run specific code outside of transaction. it runs just fine. But if   
   you put that code within a transaction - transaction fails and does a   
   rollback.   
      
   Issue has occured on different SQL versions (2000, 2008 x86 and 64bit too)   
   on different OSes (2003, 2008R2).   
      
   What I have concluded so far is... That ammount of data that is being   
   handled with specific code is not big, on contrary it's rather small, tens   
   of kilobytes and that isolation levels have absolutely no affect to the   
   outcome. It just fails every time.   
      
   Also, code is being run on one server, no network activity is being   
   triggered by that specific part of code.   
      
   Anyone, any clues? Suggestions? Ideas? Anything?   
      
   Thank you,   
   T.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)