On Tue, Nov 1, 2016 at 10:22 PM, Tony Ringsmuth <ton...@bbsp.com> wrote:
> > Are you saying that will not be allowed and thus the StandardTriggerCode > method cannot run preemptively? > Yes, If you have ANY trigger in the whole database that references ANY > restricted item (IP vars, Plugins, Various 4D commands or any method that > does), then correct: StandardTriggerCode cannot run preemptively. > (pretty horrible; isn’t it) As I understand it, if StandardTriggerCode runs inside a trigger, it can run preemptively (and trigger and code that invokes trigger with SAVE RECORD can run preemptively as well.) Problem would be if you had a wrapper around SAVE RECORD and some trigger cannot run preemptively - then wrapper cannot run preemptively (as 4D cannot know record in which table will be saved inside the wrapper.) But there is no way around this. -- Peter Bozek ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
