Truly concept of ActiveX

[LeonX]

Hi, everyone ...
I have few questions about dll:
1. As far as i know that the dll is function compound, is that right?
2. If i put a form or other control in dll project, is that out of concept?
3. Which is better put in controls in dll project or make another ocx project to handle the interface then make reference to that dll project?
Thank's in advanced.

Ferry.

[RhinoBull]

I think you are confused a bit.
DLLs are programs just like EXEs are with only diifference that cannot run as stand alone program. Just like EXE - DLL may have GUI (aka forms with controls on each of them) or could be guiless. It depends on YOUR application design. If you know that you can reuse some function more than once then it might be a good reason to develop and ActiveX dll so you can just plug it and play.
Standard dlls such Kernel or User32 which cannot be produced in VB6 are as you said "compound" of functions aka Windows API. APIs library, however, could be developed by any third party software house to interface their product (video card for instance).
What is better - dll or ocx - totally depends on YOUR needs.

Best regards.

[Dave Sell]

Hi, everyone ...
I have few questions about dll:
1. As far as i know that the dll is function compound, is that right?

Ya.

2. If i put a form or other control in dll project, is that out of concept?

I would agree that this is inappropriate.

3. Which is better put in controls in dll project or make another ocx project to handle the interface then make reference to that dll project?
Thank's in advanced.Ferry.

Keep visual components in the .OCX and keep non-visual functions bundled into the .DLL