Hello Peter.

On Oct 29, 2:18*am, "Peter T" wrote:
First of all, with things like this nothing is "written in stone"!

Oh, I know - I just grabbed the 1st expression that came to mind;-)

It sounds like your subroutine can be used without alteration by calls from
multiple class modules and can be regarded as generic. In that scenario I'd
probably put it in a normal module to be shared by all. However, if your
class module has the potential to be used as a ready made template that can
dropped into other projects, I'd probably keep such 'generic' procedures
within the class module, even if it might mean a little duplication.

Ok, I sort of suspected this.

One thing that is written in stone, fully declare all variables and head
modules Option Explicit

This one I do know, and is pretty much entrenched in my head.

Thanks for your reply, Peter. I just needed to get some feedback from
someone with more experience using class modules, just to be sure I
was on the right track (more or less). Very much appreciated.

Regards,

DaveU