Class Library

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Is there a standard way (or place) to store classes that would be usable in
many different database projects?
 
You can either make a mdb file with classes or VB dll (in case you have
visual basic). in both cases you have to add reference to corrsponding file
in order to use it
 
Sounds very good.

Can you take me thru it?

I have created a "Class.mdb" with several classes - no problem.

I start a new .mdb that is to use a class in Class.mdb. I know how to set
references in Access - will the Class.mdb come up on the reference window?
So it is that easy or do I have to register the Class.mdb somehow?

Thanks,
Mark
 
First, take at look at this.

After you've made the change to allow the class to be exposed properly, you
set a reference to the code database by selecting Tools|References and
locating your MDE containing the classes.

Note that if you change or recompile the code database containing your
classes, you must recompile ALL databases that reference it. So, creating a
DLL is really the better option. However, if the objects in your code
database are stable/unlikely to change, you'd probably be safe to reference
it in multiple projects. But remember again, if you reference the code
database in multiple databases, and make changes or recompile the code
database, you'll have to recompile all of them.

Personally, I only use code databases as a means to organize a large project
where all the component databases get recompiled at the same time anyway.
 
Back
Top