Valid from List & Label 7The List & Label OCX control can only be registered when all dependent modules are also available on the destination system. Please refer to the file REDIST.TXT in your List & Label installation path to get a list of all modules that need to be redistributed.
When the registration fails, follwing reasons are possible:
- You redistributed just the OCX but not the other dependent modules. Please refer to the file REDIST.TXT in your List & Label installation path to get a list of all modules that need to be redistributed.
- Despite of redistributing all dependent modules the registration still may fail: Probably your setup package contains all modules but they haven't yet been copied to the destination path when the setup tries to register the OCX. The setup must first copy all files. Please pay attention, that there are more modules that need to be registered than just the OCX (e.g. up to Version 13: MFC42.DLL): It is important that the registration order follows the instructions given in the file REDIST.TXT
- The setup copies the dependent modules to another directory than the OCX. If this is your real intention then the destination path for the modules must be included to the system's search path when trying to find files. We recommend to install all modules to the Windows system folder. Please take care that your setup programm does a file version check during the copy process!
- The current user doesn't have the neccessary create/write/delete rights for the HKEY_CLASSES_ROOT path in the registry. These rights are neccessary during the installation process, because any OCX registration will affect this registry path.
Hint: When the setup still isn't successfully installing the OCX try to register it manually on the destination system by using "REGSVR32.EXE \cmll??o.ocx". If any module is missing REGSVR32.EXE will show an error message.