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).



>This is very odd. The program is running under COM+ and
>the call is failing on an EXECSCRIPT() call so the filename
>will be different each time. Here is what I had written
>to my error log:
>
>

>Cannot create file \admini~1\locals~1\temp\f498085t.fxp
>

>
>>Tom, as you say, since it runs 80% of the time its not the first three possibilities. Are you sure the file name is valid when the error occurs? Or is it always the same file name? If not trap for the error in your ON ERROR and display the file name its trying to use.
>>