ActiveX controls using .DLLs - good or bad idea?

I have an ActiveX control I developed that uses several functions in a .DLL.

The web pages I use the control in carry many instances of this control.

Is there a penalty for coding the control to use functions in a .DLL?

Does each copy of the control maintain a reference to the .DLL, or only when it executes one of the functions in it?

Each seperate process, i.e. each instance of iexplore.exe, should load the code and data segments of your ActiveX control and dlls once. You will allocate more memory when you create more instances of your ActiveX control within a process.

ActiveX controls can use DLLs and, in fact, are DLLs themselves.