I have a VFP COM object that is an out of process EXE and is setup for Single Use instancing. I was assuming that this stuff was working, now I'm not so sure.

Do I understand correctly that a Single Use COM server when instanced will create a new myapp.exe process in Windows Task Manager Processess tab every time it is created?

For the most part it appears to work, but sometimes it doesn't. What I mean is sometimes I will CreateObject("myapp.application") in one VFP application and myapp.exe will show up in the Processes tab, but if I go to another VFP and do the same thing it does not create a new instance. The application space is all frucked up.

If I continue to create instances and such it starts to behave properly, but there are times when it won't.

My questions are:

1. Do I misunderstand the Single-Use feature in that by design it may create one process for my EXE accross multiple instances?
2. Is it possible the COM is still registered as a Multi-Use COM Server in Windows somehow, despite having made the change to Single-Use sometime ago?
3. What tools can I use to find out how the COM Server is registered to run?
4. How do I get VFP COM Servers and VFP COM Clients to gaurantee that a new process will be created for every instance?

Thanks.