>Maybe it's working for him because he has a SET PATH in effect while you don't?

For me it does not work at all, it really does not matter if it is in the path or not, using a expression in the #include directive gives an error, just try creating a project with only one prg and in that prg put just one line, the #include with an expression, it gives me an error every time, it does not matter the value of the variable.

But for me it is logical that it does not work, I forgot how thing work, but IIRC #include and other directives are pre-processor directives, meaning that before the compiler does its job the pre-processor will find the directives and change the source code, first it will look for any directive, first it will look for conditional directives and remove the unnecessary code, then it will look for #define and change the source to the actual values then it will look for all #include and process them the same way, this pre-processor does NOT use variables, only constants and thus you get the error (and the path is a constant at this point).

And I am like 5% sure I am right! <g>