Thank you very much, Paul. When I received the file, it was quickly
obvious that this other party had introduced an error into the file that
was producing a bunch of #0's and such and that the goal seek would never
be able to find a solution. I guess these VBA error messages are just too
gene
Getting rid of the .text and ,value cleared up the run error. However,
the activate didn't work as expected. It started writing in the input
table which is what I was trying to avoid in the first place. Is this
an excel vs vba command issue? What is the easiest way to get the
activate to switch.
