Thanks for the reply Jess....


I have been hoping to receive similar responses and to begin building a case to present to the client that it may indeed be a hardware problem.

I appreciate your response....


>snip...
>>>>Infrequently, I am receiving this error message in a VFP 5.0a distributed executable.
>>>>
>>>>I don't really know if this is a symptom of some kind of hardware problem or if it can be prevented in code.
>>>>
>>>>Any responses or experience with this error would be greatly appreciated...
>>>
>>>I think better for you to specify on this thread what functionality or processes the module is doing when the error occurs so that the problem will be easily figured out.
>>
>>I guess that is the problem I am facing....
>>
>>The error is being reported from various data entry forms (not specifically the same form or the same operation each time)
>>
>>It does seem to be related to the environment though. The error has only been reported at 2 sites out of about 30.
>
>We sometimes encounter the above problem. It is not your program but somewhere on hardware side (network card, network cable). You try to change network card first then if problem persists, try to change the connector of cable on that specific workstation.
>
>errors are: file access denied, error reading file, file inconsistency error and more which are not program errors.
>
>>
>>One of the sites was having problems with a hub on a Win95 network running a NT server back-end. They were receiving error reading file messages as well as other network related issues.
>>
>>So far, I have not found much, but I am leaning toward some problem with the configuration of temp files in the workstations.
>>
>>Here are some examples of configuration files I am using:
>>
>>Config.sys
>> device=c:\windows\himem.sys
>> device=c:\windows\emm386.exe noems novcpi
>> dos=high,umb
>> files=255
>> buffers=32,0
>> numlock=on
>>
>>Autoexec.bat
>> set temp=c:\windows\temp
>>
>>Config.fpw
>> mvcount=2048
>> tmpfiles=c:\temp
>> sortwork=c:\temp
>> editwork=c:\temp
>> progwork=c:\temp
>>
>> resource=c:\ub
>>
>>
>>Are these settings looking like they should?