>>>>>>Oops. Sorry George. Looked too fast. I was setting the value of the variable holding the calling handle to 0 as you had asked. Perhaps I should send the Desktop handle?
>>>>>>
>>>>>Hi again Bill,
>>>>>
>>>>>It's worth a try. Apparently (and this is a guess) the process is owned by the caller. Perhaps David F. or Christof can shed more light on this than I.
>>>>
>>>>Thanks for the info. I tried passing the Desktop handle and it's still hosing on me. It would seem to have something to do with sub-processes of processes or something like that. Sort of yanking the rug out from under one of the processes. But my knowledge of this stuff minimal so I'm doing a good bit groping. I wonder if using CreateProcess() would matter. I've never used it.
>>>>
>>>Hi Bill,
>>>
>>>Why not RUN /N...? If that doesn't work, You might want to look at the file (or was it an FAQ) Ed Rauh posted for launching processes.
>>
>>Hi George,
>>
>>Unfortunately this is in VB. But I'll look for Ed's info on launching processes. At any rate, if I can't find an answer to this, I'll have to rip out the "Exit All" option. Can't have it hosing my users.
>>
>
>Hi Bill,
>
>I remember this was VB about 10 minutes after I posted this. So this "Duh" is mine. You could also try WinExec(), that's old (and really CreateProcess is the right way, I believe) but it might work.

Hi George,

I think I'm gonna try my hand at CreateProcess() based on Ed's FAQ and try to learn something new. How else am I gonna find ways to mess something up? :-))

Bill