ActiveX components run in their own memory space (sort of...), but
in VB they all belong to the same thread (unless...). This to make a 
long story short. An unhandled error in a dll will crash the ActiveX
control, but not the the main application (even though it will
no longer use that control). Use error handling wisely, as suggested
already.

Regarding a shell'ed application, that is completely independent and
runs in its own memory space and execution thread.

Marco

> 

All,
I have a questions regarding the use of Active X components
If I have an ActiveX exe that call an ActiveX dll. will the ActiveX dll be 
runing in the same memory sapce as the ActiveX  exe ?
ie if the Dll crahses will the ActiveX exe also crash or will the Dll run 
in a seprate memory space?
If an ActiveX exe calls (using shell) command) a standalone exe this will 
be spawaned process Correct? So the standalone exe is in its own memory 
space?
Any suggetsion sor corrections welcomejawahar