>>
>>The key word is in bold...why take the chance?
>
>Why plan for something that probably won't happen? Sure the app has got to be clean. If the project requires eventual modeless integration, then you gotta plan for it. Why complicate it.
>

Hello Terry,

I don't think it's complicated. By default, a variable is private. Any private variable at the main program level is visible to all programs below it. So, by default, you don't have a problem...until you explicitely make a variable public.

So my question is this: Why complicate it by using the PUBLIC keyword?

Or, put another way, what specific requirement do you have that is best overcome by a public variable?