[AccessD] Would you buy

Hale, Jim Jim.Hale at FleetPride.com
Mon Jun 26 09:49:23 CDT 2006


Building Access Applications by John Viescas is an example of what you are
advocating (various common apps with a discussion of the accompanying code).
That book, which does not go into nearly the detail a framework discussion
would, is 700 pages.
Jim Hale

-----Original Message-----
From: William Hindman [mailto:wdhindman at dejpolsystems.com]
Sent: Monday, June 26, 2006 12:51 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Would you buy


...the whole point of your book is code reuse JC ...how can you demonstrate 
that with only one application?

...correct answer ...you can't.

...you need to think about this a bit ...it would make your book both unique

and of real use if you could demonstrate four different apps where more than

half the code is a snap-in framework.

...as for Sharepoint ...you're obviously not with the program ...its far 
more important to Access development than say, fixing four version old bugs 
in Access itself :))))

William

----- Original Message ----- 
From: "John W. Colby" <jwcolby at colbyconsulting.com>
To: "'Access Developers discussion and problem solving'" 
<accessd at databaseadvisors.com>
Sent: Monday, June 26, 2006 12:38 AM
Subject: Re: [AccessD] Would you buy


> >William ...take a deep breath JC ...you did ask :)
>
> ;-)
>
>>1) ...in a heartbeat (as long as I knew you had a decent editor)
>
> LOL, I don't control the editing so I can't make any promises... Other 
> than
> that it will be edited (professionally).
>
>>3) ...reusable code approached as a topic in and of itself ...lots of hat
> tips toward it but no real down and dirty how-to ...frameworks are an
> extension of that
>
> Precisely right and precisely why I hope to persuade the powers that be 
> (or
> publish anyway).
>
>>5) ...the guts of four applications from stem to stern (accounting, sales,
> pim, inventory) each done with the same framework as its heart ...using 
> A2K7
> of course ...and speaking of which, integration with sharepoint :)
>
> You don't ask for much do you.  I estimate a thousand pages just to cover
> the subject thoroughly, with a single application.  Maybe each of the
> applications you desire could be a subsequent book?  ;-)
>
>>5) ...using A2K7 of course
>
> Hmmm... A2K or greater is my expectation
>
>>5) ...and speaking of which, integration with sharepoint :)
>
> OK, NOW you're getting ridiculous.
>
> ;-)
>
> 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 William Hindman
> Sent: Sunday, June 25, 2006 10:50 PM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Would you buy
>
> 1) ...in a heartbeat (as long as I knew you had a decent editor)
> 2) ...I get by ...its easy to fool most of the people most of the time
> ...otherwise I beg for mercy here :)
> 3) ...reusable code approached as a topic in and of itself ...lots of hat
> tips toward it but no real down and dirty how-to ...frameworks are an
> extension of that ...I prefer "integrated library" but you like 
> "framework"
> ...no matter, a coherent overview is what I expect to get along with some
> red meat.
> 4) ...both ...and sound examples of when and why either is best in 
> specific
> circumstances ...I use bound as you know whenever I can ...but there are a
> number of situations where unbound is well worth the non-trivial extra 
> work.
> 5) ...the guts of four applications from stem to stern (accounting, sales,
> pim, inventory) each done with the same framework as its heart ...using 
> A2K7
> of course ...and speaking of which, integration with sharepoint :)
>
> William ...take a deep breath JC ...you did ask :)
>

***********************************************************************
The information transmitted is intended solely for the individual or
entity to which it is addressed and may contain confidential and/or
privileged material. Any review, retransmission, dissemination or
other use of or taking action in reliance upon this information by
persons or entities other than the intended recipient is prohibited.
If you have received this email in error please contact the sender and
delete the material from any computer. As a recipient of this email,
you are responsible for screening its contents and the contents of any
attachments for the presence of viruses. No liability is accepted for
any damages caused by any virus transmitted by this email.


More information about the AccessD mailing list