I created an ActiveX Control using the ActiveX Control wizard. The control uses a MFC Extension DLL that works with .EXE applications just fine, and has been deployed at customer sites for several months.
The Extension DLL contains several classes that have member functions that return CStrings from the DLLs local stringtable resources. It uses the CString::LoadString() function. This works fine with the .EXE applications, but the ActiveX control does not find the strings in its search through its CDynLinkLibrary chain.
The Extension DLL framework was built by the Extension DLL wizard. I am using VC++ 5.0
It appears that the ActiveX Control OCX is implemented like an Extension DLL and "wires" itself into the chain.
My question is: Why don't the DLL functions find their own resources AND what can be done to correct this?
Modifying the Extension DLL, except to try some things out for debugging, is not a viable option.