.... When I wrote SolvOk, SolvAdd, etc.
Hi Tom. What the op is doing is bypassing Solver's Vba code, and calling
the class function directly.
I have seen a few others mention this, but I have never understood why this
would work. The vba code portion does very little processing of the input.
It does very little, and then turns around a calls it's internal functions
using the same parameters. So, I don't know?? Using SolverOk really
should work if SolvOk works.
Sometimes placing "Solver.Auto_open" at the beginning appears to help in
some situations. But all this does is delete an internal sheet, and
rebuilds that sheet with the same small amount of data. It really shouldn't
make a difference as far as I can tell.
In the vba editor, if you pull up the "Solver" Project/Library, names like
"SolvOk" are listed on the Solver4 Class module. We use the functions on
the VBA_Function module, but then again, this does nothing more that turn
around and calls functions like SolvOK.
So, I've never really understood why the difference. I just don't see it.