Depending on how large your app is, it could be a PITA to change it, but what I do is to leave the header and footer blank in the global setup, then embed the <!-- Net:PageHeaderTag --> and <!-- Net:PageFooterTag --> in each of the procedures where and when I want them.
I just reviewed my largest app and found that I only used the header in two procedures. The footer a bit more frequently. It just started looking like more of the same after a while (which it was) and took valuable screen space.
Embedding the header and footer tags also allows you to change them out as necessary or set session variables that you can pass to the procedure.
The same applies to the menu bar procedure.
If it is easier to inhibit the call, with the number of embeds that are in the form procedure you should be able to look at the source code, then at the embed above the offending header, footer or menu, bracket the call with an IF FALSE, add an END at the embed below the call, then replace the additional code that may have been deleted with the procedure call.
Cheers!
Rob Mikkelsen