>>>I have a user that is running a Fox 2.6 application. When she runs the application, she gets a "I/O operation failure".
>>>
>>>This application resides on the network. All other users run the application without problems.
>>>
>>>Does anyone have any suggestions? Thanks!
>>>
>>>Matt
>>
>>Hi Matt,
>>
>>Does the message indicate a drive? If so, it may be that when the application was compiled, the temp files were being sent to a drive that either isn't present or doesn't have a disk in it. For example, if I compile an executable on this machine with the temp files being sent to my D: hard drive, users without a CD ROM as D: get this error; and those that do have a D: CD ROM, will get it if there's no disk in the drive. The solution is send the temp files to a local drive (or if it's a diskless workstation) to the network drive, and recompile all files. I also took the extra step of opening the project as a table and doing a replace all object with "". This cleared all references to the non-existent drive.
>
>There's a fixdrive.prg (could be in file section under fixdrive.zip) which you can run over your app/exes. It converts instances of D:, E: etc to C: - but I'd treat this with care.
>The problem happens if you develop on a drive other than C: - or if you use some of the .apps supplied with FPW (which were developed on a D: drive!)
>HTH
A client of mine had a similar problem, and I attributed it to the known problems with FPW2.x and the newer (>=300 Mhz) computers. I fixed the problem by finding the line of code that caused the error and placed a
CLEAR TYPE
=INKEY(3)
just before the offending line. My guess is that the computer somehow had a buffer overflow or somekind of a internal timeout caused by the file not being accessed fast enough for FPW. By putting the code in (you might try 1 or 2 seconds instead of the 3 that I used), it gave the I/O operations time to "catch up" with the CPU(?)
HTH
//:^)