>Jörg,
>
>Any chance there's another version of the .h somewhere along the search path, even if the correct full path is visible in the INCLUDE setting for the class?

Though probably not likely to happen nowadays, but did happen occasionally in DOS and Win9x -- the APPEND command was often a culprit when weird pathing issues came about. I also remember that a similar problem occurred if you mapped drives under Novell in a certain way (where APPEND was implicitly executed). I'd seen similar case if SET PATH was used. Of course you can easily avoid such issues by making sure you don't have duplicated files anywhere in the folders specified with the DOS APPEND command or with the FoxPro SET PATH commands..