>>>Keep your life simple and don't do that. Then you won't have to wonder which module has control.
>>
>>You guys are boring... Do not use reserved words, do not use the same procedure name, do not use form sets... no sense of adventure whatsoever!
>
>LOL
>
>IF.PRG
>* Hugo is up way too late or way too early, one or the other
>
>PROCEDURE If
>PUBLIC Browse
>DO If
>RETURN
>
>PROCEDURE If
>DO FORMSET Order TO Browse
>IF NOT Browse
> WAIT WINDOW 'What could be wrong?'
>ENDIF
>RETURN

I'd written a few programs in interpretive BASIC that I'd modified to change the variable names so that they spelled out various keywords. As long as you kept the program file in tokenized form it worked OK. Strewn throughout the program were comments warning you *never* to try saving the program in ASCII format, nor attempt any modifications. Also had similar programs that I'd used POKE to change line numbers so that they appeared in some crazy order (the tokenized format was simply a linked list -- so the sequence of line numbers didn't matter as much, save for the ones you were referencing -- you just needed to make sure that when the interpreter scanned through the program that it didn't encounter a higher number than the line number you were referencing). Again, I'd peppered the code with comments warning the user to never attempt to modify the program (if you did, the program lines would get scrambled).

BTW, the above was primarily done as a form of "copy protection" -- the code was indeed in "readable" format as requested by customer, but prevented any enduser tampering. Granted, it was easily defeated by performing a "reverse transform" so that keywords didn't occur as variable names (I could use the same program that I concocted to change the variable names in the stored BASIC file).