Loading DLL as a Out of Process

No dll's always require a client's process space to run.

    DLL will load in a Virtual memory of the current application.
    Rather than using the Virtual Memory, whether I can load it in a separate memory location like ActiveX EXE.

Hey muralic,why have you rejected my answer?
Can you load a dll out of process if so please also let me know other wise, please give me my due points.

You cannot load a dll like a exe in a seperate memory process................

To give jkunal the points you can accept his comment as an answer. If compiling it as an ActiveX EXE helps you can accept my answer.

Either way you cant load a DLL out of process.

jkunal is right, so the points are deserved.

PS - the answer is perfect. The fact that you don't particularly like the answer should not influence your grading. (Don't shoot the messenger).

To load a DLL as out of process, you need a surrogate process. This is what happens in MTS. Where the DLLs objects can be created in another machine.
Such kind of processes you can't create in VB check out VC for the same if u r interested.

VBGuru is right - you can load a DLL using a surrogate.  DCOM comes with a default surrogate.  
  To know if your DLL can run in a surrogate, check out the Registry.  It's CLSID must have an AppID subkey and that key must have a DllSurrogate value.

But still the dll is running in the process space of MTS.....