[AccessD] Would you buy

JWColby jwcolby at colbyconsulting.com
Mon Jun 26 09:08:49 CDT 2006


Robert,

>1.  	Is it totally Access based?  

Yes.  However all of the concepts can and should be generalized.

>2.	Which version?  

A2K and above

>3.	ADP or MDB?

ADPs are dead but in the end this question is not relevant.  The framework
is an MDA (a library).  Any MDB/ADP that references the library can use the
code in the library.

>Why not publish as an eBook from your website and not go to the expense of
hard copy publishing?  I would be more likely to spend $25 on that than on a
discounted hard copy from Bookpool or Amazon.

I have discovered by publishing a book that writing it is just one part of
the process.  Tech edits are critical, and the feedback is huge in making
the writing better.  And finally, having the book out on bookstore shelves
makes sales, especially if the subject is useful.  Will people copy it?  Of
course, but I won't sign those.  ;-)

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 Robert L. Stewart
Sent: Monday, June 26, 2006 9:08 AM
To: accessd at databaseadvisors.com
Subject: Re: [AccessD] Would you buy

John,

Questions back to you...

1.  Is it totally Access based?  Which version?  ADP or MDB?

2.  What DB backend?

Answers...

1.  Maybe.  Why not publish as an eBook from your website and not go to the
expense of hard copy publishing?  I would be more likely to spend $25 on
that than on a discounted hard copy from Bookpool or Amazon.

2.  Highest.

3.  Against:  Moving more toward a browser interface and ASP.Net 2.0.
    For:  For those few Access projects I would like to make them more
          efficient.

4.  Personally, I always use bound forms, but I have a friend that never
uses bound.  So, I would say it should cover both.

5.  A few years ago I started a framework application.  It included the
database, forms, and code designed to cover 80% of most applications that I
developed with Access.  What I designed was fast and efficient, simple to
add to, and to change.  I would like to see an 80% project framework out of
it.
Something that when completed, the developer could understand what he did at
each step in building it.  He could extend it easily to cover the other 20%
that specific projects demanded.  And, raise the level of expertise in the
Access developer community in general.  We still need to build a wider gap
between the "professional" developers and those that claim to be.

Robert L. Stewart
The Dyson Group International
Software for the Non-profit Enterprise
Expanding your Sphere of Knowledge

From: "JWColby" <jwcolby at colbyconsulting.com>
Subject: [AccessD] Would you buy
To: "'Access Developers discussion and problem solving'"
        <accessd at databaseadvisors.com>
Message-ID: <00d901c698bd$e5473d90$657aa8c0 at m6805>
Content-Type: text/plain;        charset="us-ascii"

1) If I were to write and get published (available at your local bookstore)
a book on reusable code and frameworks, would you buy it?

2) What is your vba skill level?

3) What are your reasons for / against buying it?

4) Would you prefer bound or unbound forms?

5) What specific things would you like to see in the book?

John W. Colby
Colby Consulting
www.ColbyConsulting.com


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




More information about the AccessD mailing list