Moving DLL

[Dorothy]

I created an Acx Dll. It worked well until I moved it to a new folder.
It says Activex Can't Create Object (when referenced from a std. exe).
I need to re-register the Dll to make it work.

Shouldn't Std. EXE application automatically detect the DLL wherever it is located?. Should the DLL be registered as and when it is moved? Doesn't this challenges the concept of Dynamic linking?

[Edneeis]

No that is the correct way. If you move it then you have to re-register it. When you register a dll part of the info stored is the dll's location, so then if you move it, it doesn't know where to look. That is part of the reason most dlls get installed to the same folder (system). The dynamic linking part is because that is what the technology does at runtime, link the library and the exe.

[Lethal]

When you create an instance of an object, the SCM will go to the registry, locate the CLSID, find the path to the component, and launch the component if need be. The registry actually holds the path to the component and it would be wise just to register it in the sys32 folder.

[Dorothy]

Thanks Edneeis..
Lethal Thanks for answering this and all the many questions posted by me.