>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>Shane, any chance that you just upgraded to 6.0 from 5.0? I had a similar problem at that point, and believe it or not, I had to "compile" the include files (I know, that makes no sense since they are straight text files). It was as if upgrading to 6.0 and recompiling the classes "unhinged" the connection to the untouched include files. I executed a COMPILE FAMEWRK.H and all was well. I don't have an explanation as to why this worked though....
>
>When you install any upgrade [VFP, SDT, CodeBook, etc.], you really should recompile the APP or EXE and check the Recompile ALL option.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>
>Yup, always do. Wasn't enough in this case, though. Not sure why -- except that the whole concept of "compiling" an include file feels wrong to start with.....

What may have happened is the include file still had the same date and time stamp from the last compile. If you make any kind of change in the file and even take back the change and save, this will change the time stamp. Then the next compile will be done on every form, class, etc., that references that file.

If the Recompile did not have an affect, this may be a bug in the project manager.