>>>>Hi,
>>>>
>>>>I have a application in 2.6 on a drive (n:)... when i make a .EXE file and i distribute this file.... some customer have a strange error "I/O Operation Failure" (or something like that)... I absolutly need to Re-Build the project on my drive C:
>>>>
>>>>Anybody can help me? or have suggestion?
>>>>
>>>>tkx
>>>Hi Martin,
>>>
>>>As was mentioned elsewhere on this thread, the problem is that the tmp files were sent to a drive that doesn't exist on the target PC. First, in you're CONFIG.FPW file add a line to indicate a directory for the tmp files on your local drive (such as: TMPFILES=C:\FOXPROW\). Just to be sure that all references are removed, I would open the project as a table and issue: REPLACE ALL OBJECT WITH "". Close the table, open the project normally, and re-compile. That should fix it.
>>
>>Hi George,
>>If he develops on a D: drive and a client has a CD Rom there without a CD in place the client will fail with an "I/O error". Fox (at Toledo) develop some of Foxpro on a D: drive so some of their own apps fail this way too (eg GenPD.app)
>
>Hi Dave,
>
>The reason I know about this is that I accidentally (don't ask how or why, it's almost embarassing) changed the location of the tmp files to my D: hard drive. All of a sudden, folks started having this problem. When I took the steps I mentioned to Martin, it got fixed.
>
>At least with GENPD.APP, we had the source code and project and could re-compile. I even modified that one so that it would recognize the system variable (I can't remember the name) that could be set for various pitches. All I had do then was open the report as a table, get the number of columns, set the system variable, and I was in business.

It was nice of them to provide the source code in those days; there was a smallish bug in GenPD too. I'm still using GenPd printing labels to Dot matrix at one site :-)

The I/O error wasn't nasty on DOS/Win3.1 machines because you could ignore it, but with the first NT Workstation and then Win95 it became a real show stopper for anyone with a CD. There's also a problem still on machines that don't have an A: drive but the BIOS sort of thinks there is one; like some IBM PCs. Funny how IBM have the least standard IBM PCs :-)

As for tmpfiles, I'm not convinced the line in Config is necessary at all. I've not used it since Foxbase or Foxpro 1.02 days. The tmpfiles directory always comes up as the local Windows Temp directory (Sys(2023)) in all current versions of Foxpro. (But I think we've been thru this before :-)

Regards