[AccessD] FMS Inc. Sourcebook

Sander,

With 19 lines of code you'd still have a 5% probability of a bug. Maybe
that's why C programmers disparage VB for being too verbose.

:) 

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

John,

you say:
"..but statistics say 1 in 20 lines of code has a bug."

If I understand correctly we have to cut up our apps in little dll's that
contain a max of 19 lines and were in the clear. We could even leave the
error handling! hahaha!!! 

Sander

--- JWColby <jwcolby at colbyconsulting.com> wrote:

> >I like it because then I can stop trying to
> remember what app I wrote a
> given function in. When starting a new app, I usually load CodeLib and 
> then copy in several standard modules.
> 
> I hate to hammer on this over and over, but that is what a library is 
> for.
> 
> Did you know that when Windows XP shipped it had SIXTY THOUSAND known 
> bugs and (more importantly) an unknown number of unknown bugs.  In 
> order to fix these bugs what does MS do?  Updates.  What do updates 
> do?  Install a new "library" with bug fixes.  Can you imagine 
> Microsoft having to rifle through your installation of windows looking 
> for the lines of code that have a bug that they just fixed and fixing 
> it everywhere on 200 million computers?  It is a silly concept and we 
> all know that.
> 
> I am sure that you are convinced that you have no bugs in your code, 
> but statistics say 1 in 20 lines of code has a bug.
> This can be something gross
> such as never ending loop (which we mostly find immediately and fix) 
> to something subtle like loss of data from a type conversion or 
> something.  By cutting and pasting your code, you cut and paste your 
> bugs.  NOW you have to remember what apps you cut and pasted bugs 
> into!  A referenced library allows you to fix a bug and simply insert 
> that fixed library into the project.  Since all your projects use your 
> lib, all your projects get your bug fixes when you insert a new lib.
> 
> I make it a policy that all GENERIC code goes in my library.  All 
> project specific code goes in the project.  If it is not used anywhere 
> else then it obviously does not belong in my library, however if it is 
> going to be used in any other project then it does belong in my 
> library.
> 
> Libraries guys, NOT cut and paste modules.
> 
> And sorry Arthur, I am not picking on you.  I see LOTS of people 
> talking about "cutting and pasting" into their projects.
> That is simply a no-no in
> modern system design.
> 
> 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 Arthur 
> Fuller
> Sent: Thursday, May 03, 2007 8:05 AM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] FMS Inc. Sourcebook
> 
> It's something that came with the Office Developer's Toolkit and also 
> with Visual Studio 6. It has a library of routines grouped around 
> topics like DAO and ADO and so on. It can contain code snippets or 
> procs/funcs and entire modules, too. I like it and still use it. Over 
> the years my own CodeLib library has swelled to contain a few hundred 
> functions etc. I like it because then I can stop trying to remember 
> what app I wrote a given function in. When starting a new app, I 
> usually load CodeLib and then copy in several standard modules.
> 
> hth,
> Arthur
> 
> 
> On 5/3/07, Sad Der <accessd666 at yahoo.com> wrote:
> >
> > Hi Charlotte,
> >
> > what's the MS CodeLibrarian. Found some articles
> on the internet about 
> > it but not much. What is this thing?
> >
> > Thanks In Advance!
> >
> > Sander
> >
> > --- Charlotte Foust <cfoust at infostatsystems.com>
> > wrote:
> >
> > > I had the 97 and 2000 versions of their
> sourcebook and never thought 
> > > it was worth the price.  The .Net product may be
> better, but I 
> > > wouldn't count on that.  I generally copy and
> paste my own code from 
> > > the MS CodeLibrarian or something similar, when
> I'm not scavenging 
> > > for ways to do something totally unfamiliar.
> > >
> > > Charlotte Foust
> 
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>