I have an aversion from long ago for semaphores so this may not be the best advise but what I'd do in these situations is create a "queu" list either in memory or records and let the file writing be done by only one process. The queu list could contain all the info necessary to pass to the process via parameters.
Most of the times when I encountered -43 was due to the Finder lagging behind the 4D call. Never had to try on Windows so not sure how it would behave there but that could be something to look for. If you trace the processes and step through the code with debugger do you still get -43? Cheers Jim Labos - infobase ----- Jim Labos - infobase -- Sent from: http://4d.1045681.n5.nabble.com/4D-Tech-f1376241.html ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
