jwcolby
jwcolby at colbyconsulting.com
Wed Jun 22 18:01:29 CDT 2011
Which implies that you don't bother using forms in Access since you can't inherit them? A tool is a tool. It does what it does and we use it as it allows. Classes do what they do and you can use them as they are intended or not. You stridently claim classes are not worth using because you can't inherit them, and yet you quietly use all the other non-inheritable objects in Access, hoping nobody notices. Classes are just a tool and I am a much better programmer being able to use them where it makes sense, and I can accomplish specific very useful things quite easily using them which would be difficult otherwise. Arthur, as I said before, I also program in C#. I have written hundreds of classes and inherited a handful. I raise and sink events, I encapsulate code and data. I do all the same things in Access classes. There are no doubt cases where inheritance would be useful in Access but it certainly is *not* in anything close to every place I need to use a class. John W. Colby www.ColbyConsulting.com On 6/22/2011 6:39 PM, Arthur Fuller wrote: > I can see your point. Back in the old days, we distinguished between O-B > languages and O-O languages, which in Access parlance is a bit of a stretch, > but the fact remains that we cannot inherit any native class. We can kludge > new classes but not inherit from any class (well, prove me wrong, but so far > as I can see, it cannot be done -- suppose I want to inherit from class > Form, into a new class ArthurForm, customize said descendant to suit (let's > keep it simple and say I want these header/footer settings, this and that > button (Save, Delete, Exit etc.), and the ability to either override or > extend the inherited methods. > > AFAIK this cannot be done in Access. Best I can do is open a generic form > and then customize it to suit the specifics. That is NOT inheritance. It is > rather a glorified Copy+Paste operation. > > A. > > On Wed, Jun 22, 2011 at 6:25 PM, Stuart McLachlan<stuart at lexacorp.com.pg>wrote: > >> No, I just don't bother with trying to use Classes in Access. >> >>