■ After installation I get Error in Module: Launch. What should I do? [1]
Cause :
Excel and What'sBest! are confused on which files to read.
Solution :
A duplicate copy of the files dformd.dll or msvcrt71.dll may be found in C:\Windows\System32. Move them to a temporary directory since they should be only in C:\...\Office12\Library\LindoWB.

■ After installation I get Error in Module: Launch. What should I do? [2]
Cause :
The keys could not be created, because of missing installation rights.
Solution :
Verify the Registry Editor and see if all the keys have been created. Create them, either by typing, or by installing with Administrator rights.

■ When starting Excel, it just shuts down. A black command window shows up before disappearing. Why?
Cause :
Excel and What'sBest! are confused on which files to read.
Solution :
A duplicate copy of the file LIBGUIDE40.DLL may be found in C:\Windows\System32. Move it to a temporary directory since they should be only in C:\...\Office12\Library\LindoWB.

■ I get the error message TEMPFILE. What can I do?
Cause :
Usually this message happens when the solver couldn't access some directories of libraries to create the temporary files. This could be due to some missing admin rights, a directory path name with symbols, or a What'sBest! 10.0 installation in a wrong Excel directory.
Solution :
Try any sample files that are located in the "C:\WB" folder. Also, running What'sBest! 10.0 with Excel 2007, the add-in is usually be saved in "C:\ProgramFiles\MicrosoftOffice\Office12\Library\LindoWB".

■ The Menu and Toolbar are not appearing, not functioning. What should I do?
Cause :
This happens when Excel cannot activate the add-in, even if it is checked. An add-in installed in another Excel directory will confuse on which library file to activate, so the functionalities of the add-in will not work properly.
Solution :
Make sure to have installed the add-in files in the corresponding Excel directory, then reset the link via the Excel Options, Add-ins, and Browse to the WBA file. Usually, the directory is:
- for Excel 2003 and What'sBest! 9.0 :
C:\ProgramFiles\MicrosoftOffice\Office11\Library
- for Excel 2007 and What'sBest! 10.0:
C:\ProgramFiles\MicrosoftOffice\Office12\Library\LindoWB

■ The Menu and Toolbar are not appearing, after installation. What can I do?
Cause :
Depending on the installation of Excel, What'sBest! may not be able to catch up the Excel directory, and so could not activate the add-in link automatically.
Solution :
Settings for Microsoft?? Excel?? 2007:
Via the Ribbon, select:
Office Button
Excel options
Popular
- Show Developer tab in the Ribbon
Office Button
Excel options
Manage Excel Add-ins Go
- Check _ What'sBest!
- or Browse to WBA.XLAM, usually in "C:\Program Files\Microsoft Office\Office12\Library\LindoWB"
Office Button
Excel options
Trust Center
Trust Center Settings
Macro Settings
- Enable all macros (possibly)
- Trusted Publishers to Lindo Systems Inc
Settings for Microsoft?? Excel?? '97-2003:
Via the Menubar, select:
Tools
Add-ins
- Check _ What'sBest!
- or Browse to WBA.XLA, usually in "C:\Program Files\Microsoft Office\Office11\Library"
Tools
Customize
Toolbars
- Check _ What'sBest!
Tools
Options
Security
Macro Security
- Security Level to medium
- Trusted Publishers to Lindo Systems Inc.

■ There are two Toolbars.
Cause :
A previous installation of What'sBest! was not successfully removed, so an extra toolbar is still showing up in the screen.
Solution :
Settings for Microsoft?? Excel?? 2007:
Via the Ribbon, select:
Right click on the extra toolbar from the previous version.
A pop up label will indicate the release number of the toolbar.
Select Remove from the sub menu.
Settings for Microsoft?? Excel?? '97-2003:
Via the Menubar, select:
Tools
Customize
Toolbars
- Select _ What'sBest! and click on Delete.

■ What'sBest! can solve a .XLS file format, but not a .XLSX. Why?
Cause :
It happens when the system is missing some up to date libraries to process and extract the new Excel file format .XLSX, .XLSM, or .XLSB. These libraries are related to the .NET environment containing the file structure parsing capabilities.
Solution :
A clean installation of Excel 2007 will solve the issue, by first removing the previous version Excel '99-2003.