David, my experience with file locks - not concurrently (in as much as you are trying to do), but generically while trying to read/write/ etc disk files:
I do not do this when testing any more $Doc_ref:=Open Document I do this: <>Doc_Ref:=Open Document Why? because when the process that opened the document is killed/crashes/etc and an explicit Close Document($Doc_Ref) command is not executed the file REMAINS OPEN (i.e. locked in write mode) forever, until a restart of 4D. as far as I am aware 4D has NEVER closed a file due to the opening process dying/aborting/crashing/or even completing in a normal fashion, if the appropriate Close Document command is not executed the file remains open, and locked for further/other writing. back to <>Doc_Ref - this way if I kill the process in which the document was opened, because it does not behave as I desire, I can close the open document from anywhere. Now this is not to say that the issue you are having is directly related, but it is, as far as I know one of those "...it is just the way 4D works..." things :( Chip On Fri, 6 Oct 2017 10:58:49 +0200, David Adams via 4D_Tech wrote: > My problem boils down to how workers deal with file locks. --------------- Gas is for washing parts Alcohol is for drinkin' Nitromethane is for racing ********************************************************************** 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 **********************************************************************
