>>>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 :-)
>>
>>Ah, but it is necessary. I mentioned that I was too embarassed to tell the story of why and how I managed to have this problem myself. Well David, it was all your fault!< gd&r >. When you and I previously had this discussion, in experimenting I elminated the TMPFILES line from my config file. Problem was that stupid here (me) forgot to put it back. No problem, except that my windows temp file directory was on my D: hard drive. Whoops! Naturally, when I turned some modifications over, all of a sudden I started getting calls about the I/O operation failure problem. The system, BTW, was five years old, and was rock solid. Anyway, in poking around the project table I discovered both the reason and the solution. Moral: Never make assumptions when you can be 100% certain that you can keep a problem from occurring with one simple line.
>>
>
>Dang; now I'll be too embarassed myself to raise it ever again :-)
>But one last poke...
>If your development windows temp dir is say D:\temp, then this shouldn't affect the users? They'll have tmpfiles auto set to whatever their windows temp directory is wouldn't they?

That's what I thought too. What happens, as far as I can figure out, is that when the executable is compiled references to the temp drive are stored in the Object memo field (and presumably into the executable code). If you open a project as a table and examine this field in various records, you'll see (among the tokens, references like c:\temp\program.fxp. In a case where this problem occurs it's usually something like d:\temp\program.fxp. And when the program begins, it's my guess, that the system tries to load that before looking internally. No drive (or disk in it), and bang I/O Operation failure.

>Reiterating your Moral in a different way, I guess there's always been so many ways to skin a cat in Foxpro that tacit assumptions about how we all set up our environments, both at development and run-time, are fraught with danger.

My wife always tells me, "Never make assumptions" (and that has nothing to do with prorgamming), but it's a good rule. How 'bout another moral: You only know what you can prove.

>All the best George...

The same to you, Dave.