>>Still... I wish there was a way to catch this as an error, no clicking.
>
>Dragan,
>Not quite understood if you want error to occur or suppress it wıth an alternatıve to "external" (which doesn't always work). To suppress (for dbc SPs and FLL functions when I don't have the FLL on hand etc) I add a dummy.prg to project with content like:
>
>

>Procedure MySomething
>Procedure MyOtherThing
>Procedure MyMissing
>

I have a bldapp.prg, which, well, builds the app (i.e. contains the "build app yy from yy.pjx" line), checks for errors (yy.err file exists or not) and then either opens the err file or runs the main app where I can test this.

However, the procedure files which may not be used at all in the build may still need to be available when running - this is a module, so it should use stuff from the daddy app. Having Procedure MyMissing may just return .t. if anywhere in the code I may have x=mymissing(). I actually may need to have MyMissing(p1, p2, p3) return an object.

The solution for this is simple - include but exclude ;) the files from the main project. The one I had trouble with is a function from a MyMain.dbc which didn't exist in mySubApp.dbc - and there was no way I could catch it and ignore it during Build command.

Luckily, I did need this function in mySubApp.dbc, so I copied it from MyMain.dbc. So it is solved for now. I just wonder what sort of problem may be there next time, and whether there may be a way for all the missing files/procedure/function/other names to be logged instead of being dialoggued ;).