>Hello,
>
> I have a FPW 2.6 application at a client site. It runs fine on all of the computers except the IBM 300 GL Personal Computers. Here, it gives me an I/O error. When I put a CD in the drive, it runs fine on the IBMs too.
>
> I have searched the threads for this type of error and found a couple of suggested fixes. One fix was to place TMPFILES and PROGWORK in the Config.fpw and direct them to the C:\ drive on your computer, then rebuild all. I did this and it did not work. Another fix was to open the project and REPLACE ALL object WITH "", then rebuild. This did not work either.
>
> If anyone has any other suggestions, I would appreciate it.
>
> For further information, this is a rather large network with one site a half mile from the server and another site a mile from the server. Computersat both sites other than the IBMs can connect and run the application with no problem. Only the IBMs are giving me the above error.
>
> The IBMs are direct from the factory PIII 450 with 32-64 megs of RAM. They have IBM network cards and appear to run fine with other networked programs.
>
> Thanks for your suggestions.

Hi Terry,

Since I am the culprit...er...author of the above information, I'll take a shot.

Obviously, something is referencing the D: (or CD-ROM drive, mine's Q:). What might be the most expedient, might be to rebuild the project from scratch and see if the problem is fixed by a completely new project.

FWIW, I currently maintain my FPW stuff on a D: drive, but send all the temp files to C:. I don't have this problem. To check to see that it's this same problem, I'd do the following. Open the project as a table, then a LOCATE on the following expression:

LOCATE FOR "D:" $ UPPER(OBJECT)

Since my stuff is on D:, I'll get found records. In examing them, I see that the path of the source file is include, but follows, the location of the compiled file, which itself is preceeded by the TMPFILES path. These are all separated by CHR(0). So, for example, a reference to the compiled myscreen.scx will read (I'm using spaces for the CHR(0)s):

c:\foxprow myscreen.spx d:\fpw26\screens\myscreen.spr

I might check to make sure that the reference preceeding the compile file name (fxp, mpx, spx) does indeed point to C:.

Lastly I might look at what, if anytime is different about those IBMs. It might yield a clue as to exactly what's happening.

Sorry I couldn't be of more help.