>>I tested this, and tested it again now.
>>Just copy those two lines into a prg and try to build a project from it.
>>
>>I don't care what help says. Microsoft never allocated enough money to make sure help is up to speed with the rest of VFP.
>
>How about...
>
>lcCmd = "dummycall()"
>eval(lcCmd)
>
>in conjunction with the external procedure? Wouldn't that allow the compiler to ignore the reference at compile/design time, but allow it to execute at runtime?

It would. But then if it was a legitimate call that I needed to be warned about, I wouldn't be warned.

OK I know I'm on a rant here, trying to make Fox behave like Cobol (don't pop up any dialogs on me, just compile, report and let me look at it when you're done), but it's simply one of those "why can't we automate this when we can automate everything else".

Reminds me of what brought me here a few thousand messages ago, "why can't we add a method to a class programmatically when Fox IS A PROGRAM and it can" - eventually, we got the 3rd parameter on .writemethod(). Now I know this is a minor thing and I'm probably the only one complaining, and holding my breath will only get me down (into a coma). I was just hoping that there's a simple setting somewhere that I forgot about ;).