>>Hi Rich,
>>
>>The problem is caused by were the temp files are stored when the EXE or APP is compiled. If, for example, you have a D: hard drive (like I do), and for some (stupid BTW in my case) set the various config.fpw items to indicate a directory on that drive, any user that doesn't either have a D: drive or doesn't have a CD in a CD-ROM drive which is setup as D: will get this error.
>>
>>The fix is simple. First, make sure that TMPFILES, PROGWORK, etc. are set to a directory on your C: drive. Start FPW after making changes. Open the project as a table and from the command line issue: REPLACE ALL ObjCode WITH "". Close the project table. Open the project was you normally would do and re-compile.
>>
>>hth,
>
>Thanks, George, but (I'm pretty sure) you're referring to a different problem. This happens regardless of where temp files are pointed on the compiling machine or the end-user machine. Config.fpw isn't involved in this problem. In my specific case, the problem apps were compiled on a machine with cd-rom D:, not HDD D:, and all temp file locations left as default (TEMP environment var if found, or Fox startup dir, correct?) On the compiling machine (and all workstations on this network, i.e. end-users as well) DOS TEMP var is C:\TEMP or C:\TMP. All workstations which use the Fox apps have Fox installed to C:\FPW26, too. So temp files on D: shouldn't be a factor here.
>
>Check out KB articles Q108165 and Q120246. MS acknowledged this as a bug in EXEs created with 2.x Distribution Kit, and fixed it in 3.0. (It also affects APPs created with 2.x Distribution Kit, but the articles don't say so.)
>
>Thanks for trying,

Hi Rich,

Nope same problem, I believe. And I also believe that what I've outlined may work. I researching the problem (which happened to me, BTW), I noted that the ObjCode field of the project contained references to: d:\somedir\somefile.fxp. The "somedir" part of that was (as I discovered) where I had indicated the temp files were. When I took the steps I've mentioned, the problem disappeared, plus the references were now c:\tempdir\somefile.fxp.

What I believe occurs (this is a guess) is that FPW is trys locate the fxp file on the CD-ROM or non-existant drive before trying to load the internal copy. If no disk is in the CD-ROM (or the drive doesn't exist) you get this problem.