you can use the flush buffer command, or you can shorten the time between automated flush buffers.
if this is writing into the very large table you mentioned in a previous post, I would insure that you do as little as possible in the trigger, and examine your indexes to determine if you use/need them. *IF* you can remove an index, or reduce trigger execution time either will help speed buffer flushing Chip On Fri, 13 Dec 2019 16:39:48 +0100, stardata.info via 4D_Tech wrote: > Hi All, > > In one my application in 4D V13.4 on Windows, in some circumstances > 4D client freezes, seems when in one process he must to write more > records. > > During these freezes periods, the 3/4 processes launched from my > applications work, but the front end interface is locked and is not > responsive. > > After some seconds or minutes, 4D client work normally. Is possibile > that this is because he must to write more records ( i think around > 100 - 300 records )? > > Is necessary to use FLUSH BUFFER commands? > > > Thanks > Ferdinando > ********************************************************************** > 4D Internet Users Group (4D iNUG) > Archive: http://lists.4d.com/archives.html > Options: https://lists.4d.com/mailman/options/4d_tech > Unsub: mailto:[email protected] > ********************************************************************** We have done so much, with so little, for so long; We are now qualified to anything with nothing <sigh> - unknown ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
