Tom. Well if its EXECSCRIPT() itself which is failing then either (1) try trapping for the error in your ON ERROR routine and issuing a RETRY if the error occurs in that specific program or (2) can you use COMPILE to compile your code first and then run the program that way? (Which is what EXECSCRIPT does anyway).


>Jos, since I am using the EXECSCRIPT() function it is creating
>the temp file names on the fly. I have NO control over the file
>names. This is VFP 7 code running under Windows 2000 and COM+.
>
>
>>Tom. The filename and path look ok. Does the file already exist at this location? If so, is the file marked read only by any chance?
>>
>>Also, I'm guessing, but are you generating the filename using the VFP SYS(3) function? If so this function will not generate unique file names within the same millisecond. In this case use SUBSTR(SYS(2015), 3) rather (which is also not full-proof but better).
>>
>>
>>