Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Modules / DAO / VBA / December 2006

Tip: Looking for answers? Try searching our database.

referencing a mdb-file

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Richard - 06 Dec 2006 22:21 GMT
I have a lot of similar code which I use in other Access applications.
So I exported the general modules to a separate database (mdb-file).
Next Iput a reference to this database in the Reference option in the VBA
editor.
This works just fine and the applications are working without a problem.
But is this the most efficient way of doing this or are there better
options?

Richard
Robert Morley - 06 Dec 2006 22:32 GMT
This is probably your best bet, though there's also the option of writing a
DLL file in VB6 and including that in your project.  The advantage to
writing DLL's in VB6 is that you have more compile options than you do in
Access.  As near as I can tell, Access uses the equivalent of Compile for
Size, whereas in VB6, you can tell it to Compile for Speed, giving you
faster execution in some cases, though with the overhead of going to an
external DLL, so there's a bit of a trade off there.

Rob

>I have a lot of similar code which I use in other Access applications.
> So I exported the general modules to a separate database (mdb-file).
[quoted text clipped - 5 lines]
>
> Richard
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.