J
James Palmer
Guest
That's a fabulous post from Rob and answers everything you need. I'd just add that we have had these issues. As a result we have a piece of code that runs every half hour or so. It sends out alarms to the relevant people if transactions are found that are older than a certain amount. That way we are getting pretty good at catching transactions as they happen so that we can track down what users are doing. The biggest culprits we have found are batch processes that message to screen (yeah I know!), and dialogues that ask the user for input within a transaction. You may well also find badly scoped transactions. If you need any help with working out strategies for hunting down bad transactions once you have found the offending pieces of code then post here as I'm sure folks have various hints and tips! 
Continue reading...
Continue reading...