>Why plan for something that probably won't happen?

Terry,

Interesting question. A numbe of years ago most apps were written to be single user. It was very rare indeed to get a request for a multiuser app. However, during those days all of my work was multiuser compliant, regardless as to whether the client had asked for that or not.

Why? Well because it actually doesn't take any more effort to make the app multiuser from the beginning than to make it single user. It does, however, take a lot of work to convert a single user app to multiuser later on. So, I chose to make all apps multiuser from the very start. The clients who eventually asked for that were quite happy that it took "so little work" to convert it.

This discussion started around the variable scoping issues. I proposed that PUBLIC was a bad practise because it has potential side effects that are hard to track down later. One example I gave was an app that later is called by another app where a public var in the called app can cause problems with the calling app. It is very easy to totally eliminate this potential problem forever, simply NEVER USE PUBLIC VARIABLES and this problem will NEVER happen.