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.

>I have a process that sometimes works and sometimes it
>does not. When it does not it, the error returned is
>Error 102 - cannot create file. The VFP reference on
>MSDN for error 102 returns the following:
>
>

>The operating system cannot create this file.
>
>The disk or directory is full.
>Remove files and try again.
>
>You do not have access to the target directory.
>Check your permission level.
>
>You specified an invalid file name.
>Check for typing mistakes.
>
>

>
>The file having problems is the result of an ExecScript()
>call and it needs to be run that way and this is running
>as a COM+ object. Since the application runs some of the
>time (probably about 80+% of the time) and the disk is not
>full, the above MSDN message is of little value.
>
>Anyone else run into this odd behavior or have a suggestion
>as to how to resolve it?