hi,

at work, we are currently upgrading from Win200 to XP and from Excel '97 to
Excel 2003. We have hundreds/thousands of spreadsheets that include in the
VBA projects code like:

Application.ExecuteExcel4Macro "Solver.xla..."

This no longer works in Excel 2003. It does not produce an error, but seems
to do nothing. The code is easy to rewrite by adding a reference to
solver.xla and calling the functions as normal in VBA. The problem is that I
would have to replace the code in all the hundreds/thousands of scientific
spreadsheets that have already been created. I need to have a solid credible
reason to tell my boss why I am going to need a lot more time to do my part
of the migration, more than just something like "I think Microsoft have
stopped supporting the old macro language". I need to KNOW. And that was
just a guess anyway. Does anyone know why the above code does not work in
Excel 2003, while it is fine in Excel'97? Also, is there a update/patch
available from Microsoft to fix the problem? Basically, is there any way I
can avoid having to rewrite the code?

Thanks in advance,
Chris