Prevent MFC ActiveX control from using DLLs that are already loaded into the process?

One option to try might be to specify the OCX's DLL dependencies as delay loaded, and then write your own delay-load helper function that used LoadLibraryEx() to be certain of loading the DLLs from the path you want to use. I have experimented with this in the past and got it to work with an executable, but I don't see why it wouldn't work with an OCX.

Knowing a bit about DLL hell, I don't know anything about "MFC Activation Context". That's why your #2 idea above seems solid.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.