- Jan 23, 2006
AC said almost the exact same thing at the end of the chapter:Most of what I've seen or read indicates it's a mindset change, but once you "get it" you'll use classes more often.
And at the very beginning before he proceeds:"Some might argue that rather than using classes, which involves constructing a framework, you could more simply have built a re-useable library. This line of argument nearly always holds; thus, the decision to use classes becomes a question of whether it seems more intuitive and natural than using a traditional code module."
I suppose if I made a living developing applications for clients, this would be a handy tool to have. As it is, I only maintain one as a collateral to my primary purpose which is logistics planning."Many Microsoft Access developers take a look at classes and then give up because they have difficulty seeing the benefit and justification for using classes. It’s true that much of what can be achieved with a simple class can also be achieved by using libraries of code, and that to build classes you often need to put in more effort during the initial development, but there are benefits in using classes that will be explored in this chapter..."
I have been watching about as fast as he can post. I really get a kick out of watching the debug process!Update: Uncle Gizmo AKA Tony Hine has posted some youtube videos dealing with OOP and MsAccess.