Hi Andrus,

It's more PM shortcoming than a bug which has it roots in the fact that VFP is an interpreter. The references to the functions, programs, arrays, e.t.c. are resolved at runtime not at the time when application is build. The thorough testing of the application is the way to find and eliminate this problem.

>To reproduce:
>

>TEXT TO cRes
>test()
>DEFINE CLASS test as Custom
>HIDDEN PROCEDURE test
>ENDPROC
>ENDDEFINE
>ENDTEXT
>STRTOFILE( cRes, 'test1.prg' )
>BUILD PROJECT test1 FROM test1
>

>
>Observed result: no error
>
>Expected result:
>
>Error
>
>Unable to find function 'TEST' referenced in test1.prg at line 1
>
>Platform: Visual FoxPro 08.00.0000.2521 for Windows
>
>Remarks
>
>Dangerous. If I include somebodys class in my code,
>I must MANUALLY check that all this class method (even hidden!) names
>are not the same as my external prg files!
>EXTERNAL PROCEDURE test.prg
>fixes this, but I'm expecting that this must be done by vfp itself.
>
>Any idea how to fix this?