Craig,

>At the bottom of your MAIN.PRG, put the following:
>
>
>PROCEDURE Dummmy
>PUBLIC aMenuDisable[1]
>
>
>You *never* call this procedure. It just keeps the compiler from complaining.

That's an awesome idea...one area where you will always get compiler errors is if you have stuff declared in stored procs in the DBC...this method might alleviate some of that...

Any idea on how to make the compiler stop complaining about function calls that call functions listed only in the DBC? For example, if I have a GetNum() function in the DBC, when I call that function from a form or class I get a compiler error that it cannot find that function. I end up having to use macro substitution just so the compiler doesn't see the name and complain...any ideas?

Thanks,
JoeK