>>This approach only works if the app NEVER dies or is
>> terminated abnormally. The client's server is EXTREMELY unstable.
>
>How about calling MEM, direct its output into a text file
>and look for the program name FOXPRO? Then you can limit
>the number of times Foxpro runs.
Interesting Idea but Foxpro doesn't show outside of it's own session in the mem/c listing.
Fred Lauckner
You know, it works on my computer. I don't know what your problem is.
.Net aint so bad.