> > Perhaps I am misunderstanding your question. Do you mean after a worker > has been killed with KILL WORKER? >
Clearly, I asked my question poorly as you and Julio both found my question unclear in the same way. (Or perhaps it's just that it's unclear to people who can speak Portuguese?) In any case, yes, I mean when a worker has been killed explicitly. I've tested out workers extensively - I've spent months on CALL WORKER, etc. and drafted a few hundred pages about them. None of that will ever see the light of day, but I've spent a fair amount of time studying them. I'm now trying to put them into production, working with the limitations they have based on the design choices that were made for this part of 4D. And bugs. The way I like to kill workers is to have a method that does it that is called from *within* the worker. This allows for a more organized shutdown. Closing files, etc. You can call the worker to execute the method in the context of the worker very easily. Tip: It's also easy to forbid method to run outside of the context of a worker with a specific name. If (Current process name # "YourWorkerNameHere") // Deal with the illegal call. Else // Do your thing End if That's a solution to a problem not everyone will run into, but it's a tidy little trick when it is appropriate. ********************************************************************** 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:[email protected] **********************************************************************
