Ray,
You could set up an Access file as a code library and import the module into it, then export code from it when needed You can also have a compiled version of the library and set up a reference to it in the VBA. With a code library, the code needs to be generic. That sometimes takes a while to design and write but having a code library can prove to be a worthwhile investment of your time.
Glenn
From: MS_Access_Professionals@yahoogroups.com [mailto:MS_Access_Professionals@yahoogroups.com]
Sent: Tuesday, November 29, 2016 1:35 PM
To: MS_Access_Professionals@yahoogroups.com
Subject: [MS_AccessPros] Finding and re-using code
Hi Everyone
I'm looking for your thoughts on this, any help appreciated. I'm finding as I code more modules, I would like to re-use that little trick again. Rather than rely on my memory that may or not remember that I solved that problem in database xyz, I'd like to save code to be found at a later date. What I'm thinking is to copy the code into a OneNote page and give it a reasonable title. I'd be able to search OneNote and copy and paste it into my new database. Is there a slicker way to have a central code store? I'm using Office 2016.
Many thanks
Ray
Posted by: "Glenn Lloyd" <argeedblu@gmail.com>
Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (2) |
Tidak ada komentar:
Posting Komentar