Actually, the utility I was working on that led me to Application.Run was a
widely distributed workbook that had to be able to be used by people on
different versions of Excel. If it's only a small group of users on one
version, then twiddling with the reference may be appropriate. Another
constraint is the fact that the VBA Project is protected in recent versions
of Excel and you can't get to it via code (oh sure, trust the users to
change that when they can barely double click on the icon to start the
program). So App.Run was the only feasible option.

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

"Jon Peltier" wrote in message
...
Whatever works, right?

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

"CodeMonkey" wrote in message
oups.com...
Thanks Jon. I saw your an earlier post with your code in and the use of
Application.Run was going to be my next port of call. However my
workaround of setting the reference using my SolverInstall routine
(thanks Dana) saving quiting and restarting seems to work at the
moment.

Cheers
Andrew