>>>Of course, this is not the same as the behavior a programmer might expect from the #INCLUDE (but which doesn't actually work). The main problem is with variables defined in the thusly "included" procedure.
>>
>>Not if you look at the original message ;-)
>
>"Public variable", indeed. I offer my apologies.

Not necessary. Happens to all of us