RobBroekhuis
Technical User
Here's an odd persistent problem I'm having. I am working through Microsoft's paid tech service to help me with this, but I figured the collective expertise here may be at least as good 
The problem is with workbooks that have macros using the solver addin. The VBProject has a reference to solver.xla, and everything works fine. Until... the workbook in question is opened using the workbooks.open method, rather than interactively. In this case, solver, when it is first called through the macro, throws a messagebox about an internal error, which stops all further macro execution. Going to the solver manually (on the tools menu) and clicking OK on the dialog (to manually solve once) works just fine, and clears the problem - further macro attempts are successful. Somehow, the programmatic opening of the workbook seems to leave the solver tool in a confused state. Has any of you seen this problem?
I'll make sure to respond to this thread if I get a satisfactory resolution through MSoft.
Rob
![[flowerface]](/data/assets/smilies/flowerface.gif "[flowerface] [flowerface]")
The problem is with workbooks that have macros using the solver addin. The VBProject has a reference to solver.xla, and everything works fine. Until... the workbook in question is opened using the workbooks.open method, rather than interactively. In this case, solver, when it is first called through the macro, throws a messagebox about an internal error, which stops all further macro execution. Going to the solver manually (on the tools menu) and clicking OK on the dialog (to manually solve once) works just fine, and clears the problem - further macro attempts are successful. Somehow, the programmatic opening of the workbook seems to leave the solver tool in a confused state. Has any of you seen this problem?
I'll make sure to respond to this thread if I get a satisfactory resolution through MSoft.
Rob
