>If VFP can't find it, it's ignored without causing an error.
Just to clarify this before it causes any confusion, what I meant, is that VFP will not give you an error on the #include line. It will not notify you that the problem is that this file can not be found, but rather crash on the first usage of one of the defined constants, which having not been defined will produce an error.
VFP does log this error if you have "Log compilation errors" checked under Tools/Options/General, but you may not see it. When compiling a project, make sure you check the "Display Errors" and "Recompile all files" and you'll get something like this when this situation occurs:
<i>TESTH.ERR File</i>
#include testh.h
Error in line 1: File does not exist.
Say_Hello
Error in line 3: Unrecognized command verb.
The name of the file will be
projectname.ERR Also, when compiling a prg an
prgname is generated.
HTH
kenweber
GCom2 Solutions
Microsoft Certified Professional