>>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.
>>
>
>Now that figures! And that's good info.


Thanks, Dave. I'm not completely sure that's what happens, but lacking contrary evidence, I think that's as good a guess as any.
>
>>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.
>>
>Then we don't know much. See my new tag line :-)

As husbands? I'm not going there.:-) Like the new line, BTW.

>Well I'm off to Tasmania for a week - it's holiday time over here.
>
>CYA

Later Dave, enjoy yourself.

PS I knew that Dragan (fellow Foxtools & Dark Beer Club member) couldn't resist this.:-)