Possibly, network connectivity problems affecting reading of that chunk of the EXE. Also, You might want to check the Windows event viewer on your client's computer, to look for possible underlying problems.

>The error (in the title of this thread) is the worst and most dreadful since it is not caused by a bug or bad code but rather the issue with the PC memory (as far as I know). I used to think that the error only happens when the app opens an external DBF file. But lately I see these error (emailed from the app) on attempting to USE/OPEN a DBF included in the .EXE
>My usual suggestion to a customer coming across this error is to reboot the PC.
>Any other suggestions on troubleshooting this error?