Universal User Functions/Portability

[LarryP]

Excel has a feature called Personal.xls where you can
write code to will be available in any Excel workbook.
Two questions in the MSAccess environment:
(1) Is there anything like a "Personal.mdb" where one can
write universal code -- functions and subs -- and thereby
make them available in any .mdb? For example, there are
some very useful Excel functions that Bill'n'the'Boyz
chose not to make common across the two applications.
(Yes, I realize I can write them in a library-type .mdb
and just copy the module into any new .mdb I build, but
I'm hoping for a simpler, don't-have-to-think-about-it
solution.)
(2) If yes, is there a way to pass that code to other
users when I send them a copy of one of my .mdb's? Or
would it have to be in a module in that specific database?

 

[Marshall Barton]

Excel has a feature called Personal.xls where you can
write code to will be available in any Excel workbook.
Two questions in the MSAccess environment:
(1) Is there anything like a "Personal.mdb" where one can
write universal code -- functions and subs -- and thereby
make them available in any .mdb? For example, there are
some very useful Excel functions that Bill'n'the'Boyz
chose not to make common across the two applications.
(Yes, I realize I can write them in a library-type .mdb
and just copy the module into any new .mdb I build, but
I'm hoping for a simpler, don't-have-to-think-about-it
solution.)
(2) If yes, is there a way to pass that code to other
users when I send them a copy of one of my .mdb's? Or
would it have to be in a module in that specific database?

Access relies heavily on the idea of libraries and you can
add your own mdb files as a library by just browsing to it
in the Tools - References menu item.

As far as using Excel functions in Access, some of them will
work, but many operate on totally different kinds of objects
(e.g. Range vs. Table, etc.) and are inherently
incompatible.

 

[david epsom dot com dot au]

No, there is no default user library that Access loads.

You can create your own libraries: you can modify your
own system so that your own libraries are loaded by
default: you can modify your own databases so that they
will try to load your libraries. Neither of these ideas
give you don't-have-to-think-about-it distribution. If
anything, they make code distribution more difficult.

(david)