DLL Hell: distribution of runtime app w/DynaZip DLL

[Reliza]

We are distributing a run-time application that includes a dll from a third
party (DynaZip). We’re using the Access 2003 packaging wizard.

Question: Is it sufficient to merely include a copy of the dll placed in the
same folder as the installed application, or is it necessary to register the
dll? If it’s necessary to register it, can we do that using the packaging
wizard?

Thanks very much.

 

[Douglas J Steele]

It depends. There are 2 types of DLLs: ActiveX (COM), and "traditional".
ActiveX need to be registered, traditional don't. Try using RegSrv32.exe. If
it works, you needed to register it...

 

[Reliza]

In addition to using the dlls, there is also an ActiveX control on the form.
When we use the packaging wizard and tell it to include the dll, after the
install the user's Access has the proper reference in the code file, but the
control on the form is not registered when you look at it from Tools in form
view. The error message the user gets is "This control has no object." This
is because it's not registered in their Access as an ActiveX control.

We are distributing this to over 200 people. Some will have Access, some
won't. Our questions are:

1. If they don't have Access, will they still have this problem?
2. Is there something we can enter into the package wizard so that for those
with Access the control will be registered in their Access?

Thanks very much for taking your time on this problem.

r

 

[Douglas J. Steele]

You may want to look into a different packaging tool. Many people find that
3rd party products are superior in this regard.

 

[Reliza]

Sigh. Will do.

Thanks very much for taking time to consider this problem.

r