Are DLLs the way to go "Jordan" <nojunk_allowed[ at ]nospam.com> 22.02.2006 03:17:55 I write a lot of utility programs and database front ends using Access 2000-2003. Most of my functions are in the modules and I use a lot of the same functions in most of my projects. Lately I have been finding that I am not updating all of the common functions in all of the projects and they are falling out of sync (what a suprize!) I have never created a DLL but I was wondering if this is something that I should look into doing since I have so many functions that are in common. If I have only been working with VBA for the past 4 years is this something that I am going to find easy to do?

Re: Are DLLs the way to go Marshall Barton <marshbarton[ at ]wowway.com> 22.02.2006 04:42:25 Jordan wrote: [Quoted Text] >I write a lot of utility programs and database front ends using Access >2000-2003. Most of my functions are in the modules and I use a lot of the >same functions in most of my projects. Lately I have been finding that I am >not updating all of the common functions in all of the projects and they are >falling out of sync (what a suprize!) > >I have never created a DLL but I was wondering if this is something that I >should look into doing since I have so many functions that are in common. >If I have only been working with VBA for the past 4 years is this something >that I am going to find easy to do? Others can probably provide the answer to your specific question, but have you looked into putting your common procedures in a separate mdb/mde and that as a library? -- Marsh MVP [MS Access]

Re: Are DLLs the way to go "Jordan" <nojunk_allowed[ at ]nospam.com> 22.02.2006 15:06:58 No I have not used that method. I could easily move all the code to an MDB/MDE. How would I link to my front ends? "Marshall Barton" <marshbarton[ at ]wowway.com> wrote in message news:kjqnv1hpm3g0rfeegssl0tsj9bjd5kkm7q[ at ]4ax.com... [Quoted Text] > Jordan wrote: > >>I write a lot of utility programs and database front ends using Access >>2000-2003. Most of my functions are in the modules and I use a lot of the >>same functions in most of my projects. Lately I have been finding that I >>am >>not updating all of the common functions in all of the projects and they >>are >>falling out of sync (what a suprize!) >> >>I have never created a DLL but I was wondering if this is something that I >>should look into doing since I have so many functions that are in common. >>If I have only been working with VBA for the past 4 years is this >>something >>that I am going to find easy to do? > > > Others can probably provide the answer to your specific > question, but have you looked into putting your common > procedures in a separate mdb/mde and that as a library? > > -- > Marsh > MVP [MS Access]

Re: Are DLLs the way to go Marshall Barton <marshbarton[ at ]wowway.com> 22.02.2006 16:40:45 Just add the utility mdb/mde library to the References in any project that wants to use the common procedures (essentially the same thing you would do if you went down the DLL route). -- Marsh MVP [MS Access] Jordan wrote: [Quoted Text] >No I have not used that method. I could easily move all the code to an >MDB/MDE. How would I link to my front ends? > > >"Marshall Barton"wrote >> Jordan wrote: >>>I write a lot of utility programs and database front ends using Access >>>2000-2003. Most of my functions are in the modules and I use a lot of the >>>same functions in most of my projects. Lately I have been finding that I >>>am >>>not updating all of the common functions in all of the projects and they >>>are >>>falling out of sync (what a suprize!) >>> >>>I have never created a DLL but I was wondering if this is something that I >>>should look into doing since I have so many functions that are in common. >>>If I have only been working with VBA for the past 4 years is this >>>something >>>that I am going to find easy to do? >> >> >> Others can probably provide the answer to your specific >> question, but have you looked into putting your common >> procedures in a separate mdb/mde and that as a library?

Re: Are DLLs the way to go strive4peace <strive4peace2006[ at ]yahoo.com> 25.02.2006 11:07:47 Thanks, Marshall! I have been wondering the same thing myself! Have an awesome day Warm Regards, Crystal MVP Microsoft Access strive4peace2006 at yahoo.com Marshall Barton wrote: [Quoted Text] > Just add the utility mdb/mde library to the References in > any project that wants to use the common procedures > (essentially the same thing you would do if you went down > the DLL route).

Re: Are DLLs the way to go "Pat Hartman\(MVP\)" <patsky[ at ]NoSpam.optonline.net> 26.02.2006 00:00:06 Libraries usually use the .mda suffix. That keeps them from showing in the open database file list. "strive4peace" <strive4peace2006[ at ]yahoo.com> wrote in message news:eTC0rufOGHA.2888[ at ]tk2msftngp13.phx.gbl... [Quoted Text] > Thanks, Marshall! > > I have been wondering the same thing myself! > > Have an awesome day > > Warm Regards, > Crystal > > MVP Microsoft Access > strive4peace2006 at yahoo.com > > > > Marshall Barton wrote: >> Just add the utility mdb/mde library to the References in >> any project that wants to use the common procedures >> (essentially the same thing you would do if you went down >> the DLL route).

Re: Are DLLs the way to go strive4peace <strive4peace2006[ at ]yahoo.com> 26.02.2006 02:21:15 Thanks, Pat! Have an awesome day Warm Regards, Crystal MVP Microsoft Access strive4peace2006 at yahoo.com Pat Hartman(MVP) wrote: [Quoted Text] > Libraries usually use the .mda suffix. That keeps them from showing in the > open database file list. > > "strive4peace" <strive4peace2006[ at ]yahoo.com> wrote in message > news:eTC0rufOGHA.2888[ at ]tk2msftngp13.phx.gbl... > >>Thanks, Marshall! >> >>I have been wondering the same thing myself! >> >>Have an awesome day >> >>Warm Regards, >>Crystal >> >>MVP Microsoft Access >>strive4peace2006 at yahoo.com >> >> >> >>Marshall Barton wrote: >> >>>Just add the utility mdb/mde library to the References in >>>any project that wants to use the common procedures >>>(essentially the same thing you would do if you went down >>>the DLL route). > > >