Hey Chip, thanks or chiming in. I've always been disciplined about opening and closing files on my own, I have no idea what 4D's defaults are on this...or if there is even a documented (promised) behavior. The traces of old, dead workers I was referring to *might* not actually exist and that wasn't what I was talking about. I'm talking closing the file explicitly, killing the worker explicitly, and then the worker is restarted. And that's when you can run into a conflict. Which should never happen, but it does.
Regarding <>whatever, you can't use that kind of variable in a preemptive process of any kind. That's one of the more painful costs of admission, but it also makes sense. ********************************************************************** 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] **********************************************************************
