F
Fernando Souza
Guest
Yes, QUIT does cause the current transaction to get committed, before exiting the session (assuming there no code trapping QUIT). When you say faulty data / data corruption, what exactly are you talking about? Is it "logical" application-level inconsistency? Or is it actual data corruption in the database that can be detected with idxcheck / dbrpr? What are the exact side effects of this corruption. I just wanted to check if this is an application issue or a product issue. What OE release are you running with? As far as stopping that process, as you alluded to, STOP can be trapped by any ABL code so that is not a reliable approach. Very few stop conditions are not trappable at all (for instance, a Lock table overflow cannot be trapped).
Continue reading...
Continue reading...