Mark,
Creating a DLL library in VB6 would be much more straightforward as you
already have the classes etc in VBA and much would be just copy/paste. Once
in compiled format though you would need to enforce Binary Compatibility,
otherwise you will break the library's use with each upgrade; assuming you
are setting a reference to the library.
If you want to use a .Net product it will (probably) involve a re-write in a
(essentially) different language.

NickHK

"Mark Olsen" wrote in message
...
Hi,
I am using VBA in excel to create a program that queries a database and
fills out excel spreadsheets. I have made a list of Classes that I use
and
need to be able to use the same classes in several different projects.
Earlier I asked a question about how to create a "library" so I could have
all of the classes in one place. I got a great answer about creating a
new
workbook containing the classes that I would reference. However, I still
dont get some of the more object oriented features of the new versions of
Visual Basic. I was wondering if I could use Visual Basic 2005 Express
Edition or the Full Visual Basic .NET to create a library that I could use
from VBA. Is this possible? Is it worth it? It seems that this would
make
maintaining and distributing the code a lot easier. Can anyone give me
any
input?