>I like a clean look in programs but there are times when troubleshooting problems or locating where something specific occurs in a program is time consuming and frustrating when you have something like the below which starts to resemble the 'GOTO' command:
>

>*some processing
>
>Do program1  && program1 calls program9 which calls function2, function9,etc
>Do program2  && program2 calls another procedure and function, etc.
>Do program3  && etc
>
>*some more processing
>
>Do program4
>Do program5
>Do program6
>
>*etc
>

>It's ideal to have commonly used functions in their own prgs or a procedure file but in some cases I have seen every single function and procedure in a separate prg and not only were there literally hundreds of prgs in the project but I was forever opening up separate prgs locating stuff...

Tracy,

The problem is not with the princples, but rather the design. If the design had adhered to the principles, then you wouldn't be having the problem.

Well designed system make it easier (because of information hiding and functional cohesion) to debug situations like this.