[AccessD] FMS Inc. Sourcebook

The difference is that libraries in managed code are compiled into a
dll.  Once that happens, they are no longer available to be messed with
by the curious, and they are true libraries, as opposed to mdbs with a
different name and a breakable reference in the tools menu.

You are willfully misinterpreting what I said in order to prove your
point, but I've totally lost track of what the point was!  I'm not
arguing that libraries are bad, so why are you arguing with me and what
am I supposed to give up on??

Charlotte Foust 

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

Charlotte, 

A library is a group of code, the source stored (and more importantly
MAINTAINED) in one location but used in more than one place.  Tell me
how that is different?

There is no foul here.  Access is the ONLY Office application that
allows libraries but they are indeed libraries.  A group of code, stored
and maintained in one location but used in more than one place.  Because
they are stored in one location, you fix a bug one time, at that stored
location, and then distribute the fix version to the other locations
where the code is used.

Now I understand that with a versioning system you can get into issues
there but that is an intentional step that you take because you have a
reason to have more than one branch of the code.

And if an Access library (which they are called libraries inside of our
programming environment) is not a library, how much more "not a library"
is a "cut and paste" exercise?

I am discussing a simple concept here, which you KNOW is "correct".  I
did not make this up, I have no vested interest in you or anyone else
using it.
It is a concept taught and used throughout the industry.

C'mon Charlotte, give it up.

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 Charlotte
Foust
Sent: Thursday, May 03, 2007 12:38 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] FMS Inc. Sourcebook

FOUL!  Libraries in managed code aren't anything like Access libraries
and you know it!  Grrrr

Charlotte Foust 

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

>And that my friends is why the .NET managed code libraries make a lot 
>of
sense. :)

Notice the use of the word LIBRARIES.


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 Eric Barro
Sent: Thursday, May 03, 2007 11:53 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] FMS Inc. Sourcebook

And that my friends is why the .NET managed code libraries make a lot of
sense. :)

Combine that with n-tier approach and the software development life
cycle is less painful to manage. 

--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com