[AccessD] Autonumber Assigned Immediately

I grew up in Yuma.  Actually out in the Bard valley (over in California)
about 12 miles from town.

John W. Colby
www.ColbyConsulting.com 

Contribute your unused CPU cycles to a good cause:
http://folding.stanford.edu/

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Robert L. Stewart
Sent: Friday, September 09, 2005 8:03 AM
To: accessd at databaseadvisors.com
Subject: Re: [AccessD] Autonumber Assigned Immediately


A lot of the referrals that I get are from people that used people that
think they are Access programmers, but know nothing about database design
and the  applications they write require a complete rewrite to actually
work. I have to go in and FIX the disaster that the client ended up with.

When I worked at the Army proving grounds in Yuma, we had a saying. "It
takes an engineer to tear something apart, but a good technician to put it
back together again."

A well thought out design is not over-building.  But, it also will not have
to have any major changes over the years because of the thought that went
into it.

Sounds like you thought it out if it has been running that long. :-)

Robert

At 08:54 PM 9/8/2005, you wrote:
>Date: Thu, 8 Sep 2005 19:44:04 -0500
>From: "Reuben Cummings" <reuben at gfconsultants.com>
>Subject: Re: [AccessD] Autonumber Assigned Immediately
>To: "Access Developers discussion and problem solving"
>         <accessd at databaseadvisors.com>
>Message-ID: <DPEKLCIHBOJKCKJECLCPOEFACGAA.reuben at gfconsultants.com>
>Content-Type: text/plain;       charset="us-ascii"
>
>It can also be called over-building.
>
>I have an app that works perfectly and has done so since 2000.  I wrote 
>it with simplicity in mind.  I had it ready for use in 6 months with 
>very minor bugs.  I sold that app to an engineering firm that thought 
>"building it right, the first time" was the way to go and immediately 
>set out to completely re-write the app.  The purchased the app in March 
>of 2003 and in October of 2004 gave up with nothing that worked and 
>gave the whole thing back.  They thought they needed to build 
>everything to "the right way" - they were overbuilding the project.
>
>The question is "Who decides what the right way is?"  Is it mine that 
>works perfectly and is technically fine and has been making me good 
>money since 2000...or the engineers that was written by the book, but 
>never worked and therefore never produced a penny?  BTW, I've seen the 
>details of their work records and they have over $300,000 invested in 
>programming time.
>
>Getting stuff to the market is sometimes more important than "perfect" 
>code or design.  Ask Netscape how writing perfect code worked out for 
>them.
>
>I'm not a programmer - at least I don't consider myself one.  I have 
>never had any formal programming training and therefore have never been 
>caught up in books and such.  I simply build stuff that works.  If my 
>clients are happy and I'm making money I have to conclude the design is 
>just fine.
>
>Reuben Cummings
>GFC, LLC
>812.523.1017


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