Dana -

Whenever I record a macro using Solver, if it records setting of constraints
it puts SolverOK both before and after the constraints. I usually delete the
first, but just to streamline the code. I haven't noticed any issue with
running the code with either or both SolverOK statements, it just seemed
wasteful to have both, and seemed to be logical (like that should matter) to
put SolverOK after the SolverAdd's.

FYI, I recently posted a page on using Solver with VBA, and I'd appreciate
any suggestions from someone with your knowledge about Solver. If you have
any comments, use the email link at the bottom of the page:

http://peltiertech.com/Excel/SolverVBA.html

- Jon
-------
Jon Peltier, Microsoft Excel MVP
Tutorials and Custom Solutions
Peltier Technical Services, Inc. - http://PeltierTech.com
_______


"Dana DeLouis" wrote in message
...
second suggestion did the trick.

Hi. Glad it's working. :) Nothing like a good guess.
For my own education, was the solution the dropping the second SolverOk?
The reason I ask is that others have also posted code where there were two
SolverOk's.
They also reported that they "recorded a macro" to get the code.
If so, I wonder if there is something that triggers an error with the
recording of Solver macros?

--
Dana DeLouis


wrote in message
ups.com...
Hey Dana,

thank you very, very much for your suggestions! Although your first
guess about Excel 2000 was wrong (actually using Excel 2003), your
second suggestion did the trick.

Thank you once again.

David