Hi Stephen,

valid reasoning <g.
thx for sharing your thoughts.

--
keepITcool
| www.XLsupport.com | keepITcool chello nl | amsterdam


Stephen Bullen wrote :

Hi KeepITcool,

Are there any disadvantages to using thisworkbook object module as
the container of application event code?

To me, it comes down to encapsulation - having one module do one
thing and do it well, so I can copy it around and reuse it in other
projects almost unchanged. So having one class that handles
application-level events and only handles application-level events
makes more sense to me than having a class that contains a mixture of
book-level and app-level events.

On the other hand, if I think functionally rather than in terms of
'levels', I could easily imagine a class that does a specific
(high-level) 'job', but to do that, it needs to respond to both
app-level and book-level events.

Regards

Stephen Bullen
Microsoft MVP - Excel
www.oaltd.co.uk