What if you run the code from Excel instead of from Word .
See what happens.

NickHK

"russian_hamlet" wrote in message
ups.com...
All the files are different. File3 contains a macro, but nothing that
should affect this.
I have tried the files in various orders ...

File Order Bombs at
1234 2
123 2
134 no bomb
1324 2
1342 2
2134 1
2413 1
4132 2
4321 1

The logic seems to be: (1) never bomb the first file, (2) bomb the
first File1 or File2 moving backwards from the end, i.e. utter rubbish.
I therefore suspect the files are up the wrong tree, so to speak. There
is nothing unusual about them, anyway.
And there is nothing obviously wrong in the code. It even works on some
(Windows 2000) machines.
I am worried that I'm perhaps not cleaning up my objects properly,
although I have stopped the code before and after each file closes and
it always gives a objExcel.Workbooks.Count of 1 and then 0 ...