I have a VB6 dll wrapper that wraps around an ocx that wraps around a non-com windows dll. Although the ocx and non-com dll sit in the same folder, the ocx cannot load the non-com unless it (the non-com dll) is placed in system32.
Why is this, and how can we force the ocx to look for the non-com in the same folder as the ocx?
A few details:
- Both the ocx and the non-com are vc++ and were not written by me, but by another programmer at my company
- I asked the programmer to put ".\" in his loadlibrary in the ocx, hoping it would see the non-com in the same location - didn't work
- when the non-com is in system32 it works, otherwise the ocx is unable to load the non-com and it fails