No - that was my first instinct also. The file opens as it should, but the
assignment doesn't work. Also, I have just discovered that the assignment in
this step works fine when I set a breakpoint just past it and hit continue,
so obviously stepping through in debug mode is the culprit...
This also happens when I attempt to step through running a macro in another
workbook, like so:

Application.Run "Summary_temp_Thpt.xls!Update"

The exact same thing happens - execution will not move any further unless I
hit continue...
--
There are 10 types of people in the world - those who understand binary and
those who don't.


"JLGWhiz" wrote:

Is there anything in the fNameOut variable besides the actual path and file
name? That would be the only thing that could be causing the problem.

"Geoff" wrote:

I have just encountered an error where stepping through code, the following
assignment statement fails:

Set fOut = Workbooks.Open(fNameOut)

fOut is a workbook variable and fNameOut is its name - basically the
workbook opens fine, but the value of fOut is Nothing. When I try to step
into the code from this point, the program refuses to go any further. There
is no error message, and execution refuses to move past the highlighted line.

--
There are 10 types of people in the world - those who understand binary and
those who don't.