[AccessD] FMS Inc. Sourcebook

That is indeed an interesting tidbit.  So far I have not done any work
directly in the other office applications.  I have saved code in modules in
Excel, but I have only ever used it by calling it by automation.  It is
probably useless info to me but if I ever do just have to do work in the
other apps it will be good to know.

John W. Colby
Colby Consulting
www.ColbyConsulting.com

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Hale, Jim
Sent: Friday, May 04, 2007 11:11 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] FMS Inc. Sourcebook

<I can put a bunch of code modules into an Excel file, an...> Now THAT is an
interesting tidbit from this discussion. I'll have to play with that one. As
far as cut and paste is concerned I have to agree with John. Personally I
think cut-and-masking tape is much preferable. :-) Jim Hale

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Heenan, Lambert
Sent: Thursday, May 03, 2007 1:47 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] FMS Inc. Sourcebook


I'm on Charlotte's side with this one. :-)

A "library" is a grouping of executable code which can be linked to or have
references set to and the code within becomes available to the client
application. No cutting and pasting involved. The point being that the code
in question is immediately usable by the client once the linkage has been
established. There's also no cherry picking of code routines to make
available. Link to a library and you get it all.

Typically, whenever a library file is modified in any way all the client
applications need to be recompiled as the references/jump tables (or
whatever else is used behind the scenes to define the code entry points)
will have changed.

"<snip>
Access is the ONLY Office application that allows libraries but they are
indeed libraries. 
<snip>"

I can't agree with that statement either. I can put a bunch of code modules
into an Excel file, and in the VBA IDE I can set the project name to
something other than "VBAProject". After I save the Excel file I am then
able to set a reference to it in another Excel and the (public) routines in
the referenced file will be available for use. I have a library.

Lambert