Why not? It isn't supported? I just checked In Transaction in trigger is a preemptive compliant. It means, preemptive mode does expect transaction. Any hidden constraint?
Without transaction, trigger is meaningless. When a trigger invoked, mulitple tables might be updated inside the trigger. When trigger was rejected, other updated tables won't roll back except the trigger invoking table. This would cause serious data integrity issue. Alan Chan 4D iNug Technical <4d_tech@lists.4d.com> writes: >transactional data entry is kind of task you would typically want to avoid >using preemptive mode. ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
