Geezz, shame on me!...

Thank you, Jim, for pointing me that and for being attentive. You're absolutely right: that is a #include limitation I wasn't aware of (took for granted from other languages experiences). I'm sure next time I pull out some "clever" trick I'll put it through test bed prior to submission.

And, of course, apologies are due to Alex.


>>You can put

>>#include "some.prg"

>>in stored procedures. Stored procedures defined in the included file won't appear in the project manager but can be indirectly edited (for easy editing, you could put them in the Code area and exclude the file).
>>

>
>Is there something special about an #INCLUDE in a .DBC? The VFP7 Help for #Include says:
>Only the #DEFINE ... #UNDEF and #IF ... #ENDIF preprocessor directives are recognized in a header file. Comments and Visual FoxPro commands included in a header file are ignored.

bye