Some wonder why TR was built others say it works fine. I thought I had a good handle on TR but now reading the differing opinions I am questing my understanding of TR.
Some posts indicate it is completely useless and can't be trusted. Some other indicate like a weapon as long as you treat it with respect and know how to you it you'll be fine. So off the the archives I went: http://ars-action-request-system.1.n7.nabble.com/TR-vs-DB-sanity-check-please-tp99981p99993.html Doug set it straight in 2010. After rereading his post I am questioning the purpose of TR. QUOTE: 'A' != 'DB.A' is all the testing you need to see if the value has changed If DB all that is needed what is a valid use case for having TR. Not one that can be down with TR or DB but what is that TR provides that cannot be done otherwise? Jason BTW, hope this didn't post twice. I used the web UI because of the recent email issues but when I checked I don't see my reply which is usually instant on the web. I waited a few minutes and fired again. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
