JWColby
jwcolby at colbyconsulting.com
Mon Jun 26 06:48:50 CDT 2006
William, >...the whole point of your book is code reuse JC ...how can you demonstrate that with only one application? The framework is about building applications of course, but what it is really about is two things: Providing services to the application. If I can provide FTP or Zip or MD5 encryption or Sysvars or Light Weight Security in one app, I do not need to demonstrate that again in a second app. Automating the handling of form and control events to provide "instant" forms, which operate in a consistent manner across an application. If I can demonstrate (for example) NotInList event handling for a combo, or JIT subforms in one form, I can demonstrate the exact same event handling (if necessary) in a second form. I do not need a second app to demonstrate that. There are several very fundamental problems with building the guts of 4 apps in a book. 1) I would have to know and understand those apps, do the business analysis to determine the entities and business rules etc. I would then have to take the time to build the applications, create all the tables, queries, forms and reports and code to implement the business rules, not to mention generate dummy data. 2) Assuming that "half the code is snap-in framework", that means that 1/2 the code ISN'T. If it takes me the better part of 9 months to write the book about the framework, and I have to develop the other 1/2 of the code (and write about it) for 4 apps, all of which equal the amount of code in the framework... That's 36 months developing and writing code for apps (which I don't even understand the business rules for and don't have a client using so I can pick their brains...) plus the 9 months for the framework. 3) I would have to have the room in the book to show the 4 apps. 4) I would have to write about my entire framework which, all by itself, includes much more code than will fit in a single book about frameworks. What I CAN do is work with 4 individuals who, having read the book, want to apply the framework concepts to their application and make a demo of their application available to the public via my (or a link to their) web site. What I WILL do is take my billing program and use it as a demo for using the framework. It currently uses my second generation framework so I would have to retrofit it (or perhaps a rebuild is in order?) to use the current framework. >...as for Sharepoint ...you're obviously not with the program Uhhh... Nope >its far more important to Access development than say, fixing four version old bugs in Access itself :)))) Uhhhh yep. To Microsoft. ;-) 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: Monday, June 26, 2006 1: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 :) > > ----- Original Message ----- > From: "JWColby" <jwcolby at colbyconsulting.com> > To: "'Access Developers discussion and problem solving'" > <accessd at databaseadvisors.com> > Sent: Sunday, June 25, 2006 9:14 PM > Subject: [AccessD] Would you buy > > >> 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 >> > > > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com