This works great - with a few notes.
You don't have to rename the old class and create a new one. You can just
delete the code and import the text file.
When you import the text file, these lines will appear at the top. Just
delete them (unless someone knows something I don't).
VERSION 1.0 CLASS
BEGIN
MultiUse = -1 'True
End
Also, if you have any private classes that are used as parameters in the new
public class (paramaters and other stuff - you'll see in the error message),
you have to expose those classes as well.
But overall this is really GREAT!!
THANKS!!!
"Marshall Barton" <ma*********@wowway.comwrote in message
news:ns********************************@4ax.com...
Matthew Wells wrote:
>>I have an mdb with class modules that I use as a reference for another
mdb.
The library is called MyLib.
I'm trying to declare variables in my front end mdb as class objects in
the
library
Dim x as MyLib.ClassModuleName
This doesn't seem to work. When I type MyLib. and the intellisense pops
up,
all I see are public functions and enums. I don't see any class module
names. How do I expose them?
Take a look at:
http://www.mvps.org/access/modules/mdl0034.htm
--
Marsh