Hi all,

looking at a difficult situation... the set up first, then my
impressions second:

macro usess shell command to run an executable, which makes a barcode
image, and leaves desired output in a predictable place. Or rather is
supposed to.

The macro then makes use of this output.

This macro works on my Win XP Pro system. (Office 2007)

This macro fails on my Windows 2000 Pro system. (Office 2003)

What appears to be happening is that in the latter case, the
executable is being prevented from writing the file. When I abort the
macro, suddenly the file appears.

No amount of waiting solves the problem. It is as if the output is
blocked from the executable while the vba code is running.

Can this be accounted for in the operating system? Or maybe the
different office versions?

I'm not sure where to turn at this point! Going a bit nuts :)

Thanks for your kind help,

SMS

I'm sorry, one correction... the offending (older) system is running
office 2002 components.

Thank you again for your help!