A common scenario is that we may want to have an object variable that we need to be able to refer to from several different parts in our application. It's tempting to just use a public variable but this is not without its problems. For one, we can't be certain it's ready to use, hasn't been closed or otherwise dropped out of scope. Thus a good technique is to write a Property procedure as thus:

By using the technique we free ourselves of worrying and checking whether it's been initialized. The technique is not restricted to ADO and can be used for other libraries.