>>I did this a long time ago and I haven't changed it because I think it works well.
>>
>>I also have other sections of code that have tightly coupled routines. But they are routines that will never be used elsewhere. Sometimes it is just to get a chunk of code out of the way. Like, these 50 lines basically do one thing, so make them a procedure called OneThing and when reading the code (in the calling routine), it looks cleaner (ie. do OneThing as opposed to 50 lines of code with a comment saying * This section does one thing). Will the called procedure ever be used elsewhere? No. Is it too tightly coupled to be used elsewhere without great difficulty? Yes. Do I lose sleep over it? No.
>>
>>I think there are always exceptions to the rules. Of course, generally, I agree with the rules.
>>
>>Take care,
>
>Joe,
>
>Tight coupling is not a problem within a module. A module can be comprised of many routines that only work together. The outside world sees only the module and knows nothing about how the module is built inside. This is called cohesion, that is having a number of routines that together comprise one module in the code. The coupling of the routines inside the module is irrelevant to the overall reuse of the module.

Awww, my rebel image (self image) has been shattered.

What do you think of the MakingEXE public variable? Do you see it as a problem? Or a better way of doing it...other than as a property of the application?

Take care,

Joe