Error phenomenon: after adding non-negative constraint to solver, the calculation result is still decimal


Solution:
uncheck ‘ignore integer constraints’ in the options of the solver

integer results appear:

SLOVER installation manual:
① file -> More-> Options

②Add-in

③ Bottom go

④ Check solver add in and confirm to save

⑤ solver will appear in the upper right corner of the data toolbar

Error phenomenon:
the computer with 64 bit Office installed will prompt that the macro is not available after installation

even options -> Trust Center -> Credit center settings -> Macro settings -> Enable all macros and still prompt the same error.

Solution:
① the solver cannot be installed on a 64 bit computer. You can uninstall the local 64 bit office and reinstall 32-bit office.

Or

② Install VMware, build a win10, install an office 32-bit system on the virtual machine, and open network sharing and shared folders
(1) VMware installation reference: the latest super detailed VMware virtual machine download and installation
VMware official website: VMware download
(basically the default installation)

(2) Install virtual machine win10
VMware virtual machine install windows system

(3) Setting shared folders for virtual machines
VMware sets shared folders for windows virtual machines

(4) Virtual machine settings network
I found many strategies and didn’t understand
it turns out that it’s actually very simple
when the virtual machine is turned off, select Edit virtual machine settings

then select network adapter, check bridge mode and copy physical network connection status

OK, turn on the virtual machine again and find that the virtual machine can access the Internet normally

(5) the last step is the installation of 32-bit office
Microsoft Office
come to an official website link, download and install, and finish it.

Error phenomenon: when solver uses simple LP, it cannot find a solution satisfying constraints
tips can be answered using GRG nonlinear

Solution:
GRG nonlinear is selected for the solving method

After testing, even if the constraints input expression is correct, different solving methods will report errors.

For the differences between the three solving methods:

1. Will build a linear programming model, using the Simplex method;
2. Solving speed: Simplex> GRG> Evolutionary
3. GRG may not get the global optimal solution, use Evolutionary to get the global optimal solution;
4. Using GRG combined with Multistart can get a better local optimal solution.

in short, when an error is reported, if there is no problem with the constraints after the inspection, change the solving method

Error phenomenon 1: when the cell is set to text type, simple LP calculation using solver will prompt some cells are not data (some message like this)

solution: selected!, Coerce text of type text into number (convert to number) before calculation.