That seems a slick enough way, but another way is to have a wrapper class
that is exposed to the workbook which handles all of the other classes. This
class would know about the other classes, the workbook code wouldn't, and
would route all the request to the class through the wrapper. Probably not
any less more (maybe even more), but it would clean up the workbook code,
and abstract the class code.

--
HTH

Bob Phillips

(replace somewhere in email address with gmail if mailing direct)

wrote in message
ups.com...
First of all thanks Bob for you answer which did address my original
problem.

Thanks Dave for guidance towards an "Add-In". This makes life way
easier

Im able to call the InitialiseConfig() method living in my Add-In from
the WorkBook_Open()

Im also able to reference the methods other in the Add-In in my VBA.
By setting a reference (Tools - References command )

The true benefit is that an update to the Add-In becomes available to
each Spreadsheet that references it the next time it is opened

i.e. change code in one place but used in many places (updates
automatically available)
just what i was looking for

:-)

Thanks Guys

A wee side question

I place a list of classes in my Add-In

eg.

AxaSpecific.cls
CMSpecific.cls
FPSpecific.cls
GESpecific.cls

Depending on which Workbook you open

i.e.

AXAimport.xls
CMimport.xls
FPimport.xls
GEimport.xls

I want to instantiate the appropriate object

currently i use something like

Select Case UCase(Left(ThisWorkBook.Name, 2))
Set providerSpecific = New AxaSpecific
Case "CM"
Set providerSpecific = New CMSpecific
Case "FP"
Set providerSpecific = New FPSpecific
Case "GE"
Set providerSpecific = New GESpecific
.
.
.
Case Else
End Select


Is there a slicker way as my case statement has many more options