It appears that in the public VFP 9 beta a change has been made to how #INCLDUE is processed for PRG files. In VFP 8 and earlier, if I wrote

#INCLUDE "INCLUDE/APPINCL.H"

it would find the file if was relative to the current folder or in the path even when the PRG was not in the current folder. In VFP 9 it does not find the include file and gives no error message that it could not find it. If the path is relative to the folder where the PRG is located it seems to find it OK.

Also: In VFP 9 if I #INCLUDE a non-existant file it doesn't complain at all when I compile the PRG. VFP 7 and 8 complain about not finding the file.

(This change broke my CodeBook 6 framework as it has that include in Utility.prg as well as several other common PRG's. I'm not sure why CodeBook is set up that way and am investigating that right now. It seems wrong to me, but apparently goes back to CodeBook 3. I'll look at it a bit more to see if it makes sense to change the PRG's to include FRAMEWRK.H instead, but this still looks to me like a change in the behavior of the #INCLUDE in VFP 9.)

...Jim Hansen