Hi Paul,
I didn't had problem with macro security before.
I suggest you step(F8) trought your code with the locals window open and
check the value of your variables and see if one woudl be changeg by
something (...?).
For info, what is you current degree of security ?
Good luck
Regards,
JY

"Paul Mac" wrote in message
...
Hi Jean,

I have tried:

- Setting the wb Variable as you described
- Using the Open FileDIalog.show (then . execute)
- Just trying workbook.open all by its lonesome.

All with no luck. It appears that as soon as the workbook is called, it
stops the current code.

I have constructed a workaround by using the Application.Ontime method and
calling a sub-set of the code after the point where it stops.

Any other ideas would be great.

Paul.