Not sure if this is the right forum to post a SOLVER question, so feel free to redirect me if there's a better place.

I've created an "inputs" section of my worksheet specifically for Solver. It is a small table with two columns. The first column is the label. Second column is all integers. This is the "input" section. (where I need a real number in my formulas I simply multiply the # in the second column by .01 or other partial #).

I created the second column with all integers so that Solver would not need to go through millions of real numbers to find the optimal inputs. I was hoping this would significantly reduce the amount of time Solver takes to reach the best possible combination of numbers.

As an example: A constraint says find an integer with an upper bound of 300 and a lower bound of 0.

What I'm discovering is that Solver is iterating real numbers even though I've specified integers. Instead of running from 0 to 300 in integers e.g. 0, 1, 2, 3 etc. It is running numbers with 12 decimal places (e.g. 1.019853879534).

I'm using the Evolutionary method since that's the best approach for my workbook. I don't know what the two "precision" settings in Solver really do. I've reduced them from the default (about 8 decimal places?) to one. But that has no visible effect.

Usually, when Solver finishes its work, it does stop at an integer. But there are times when it stops at a number with 12 decimal places even though I've set it to run just integers.

Anyone have a suggestion? Thanks!