Charlotte Foust
charlotte.foust at gmail.com
Wed Jun 22 18:16:52 CDT 2011
John, I really believe it is, like religion of any kind, a very personal preference. Like you, I always saw the benefit of classes and readily took to them. But that's because we're thinking in terms of objects, black boxes, widgets, whatever, and simplifying life down the road. Since those are fairly recent additions to the toolbox for database developers, Access or otherwise, it's to be expected that not everyone is comfortable going there. For years in my last job, I wasn't allowed to use classes because my boss felt it would be too difficult to rewrite pieces of our commercial Access applications to use them and he wasn't convinced of their usefulness. Of course when we went to VB.Net, the argument disappeared, because it made no sense to do it any other way. Different strokes .... Charlotte Foust On Wed, Jun 22, 2011 at 3:41 PM, jwcolby <jwcolby at colbyconsulting.com>wrote: > >> I have followed JC's threads and implemented them, but it is a lot of > work, in several different modules. > > OMG it probably took me three minutes to set up. > > Writing the entire clsMsg took a few minutes. You have to admit it is a > trivial class. > > I have reused that class for 10 years. > > Writing the module to hold the global pointer took... oh... about 3 > minutes. I have reused that module for about 10 years. > > Calling the message class from the city subform took another 30 seconds. > Setting up a form to sink the class took about another minute. So my time > spent in this specific project was about 2 minutes and 30 seconds. > > You are indeed getting old if that is too much work. > > ;) > > Why is it that I am able to easily use them but you aren't? I am not > particularly skilled, or particularly knowledgeable. > > The reality is you don't like the solution so you make up all kind of > reasons why not to use classes. But they are just your reasons. You appear > to throw away a very powerful tool because you are mad at Microsoft for not > giving your inheritance. > > Classes work. They do exactly what they claim to do in VBA, encapsulate > data and code and sink and source events. They are just dead simple to > create and use. > > You like checking if forms are open and calling specific controls on > specific forms from the source event. You said that is your preferred > solution, and anyone who wants to do that is certainly welcomed to do so. I > truly don't care Stuart. I used to do that myself before I discovered how > trivial it is to raise and sink events. Now I don't do that anymore. I > haven't twiddled controls in other forms for 10 years and it makes no sense > to me to do so but if you like that, knock yourself out. > > You are of course welcome to jump in the thread and let us know how you are > pissed at Microsoft and so refuse to have anything to do with classes. But > the solution works, and works at least as well as checking whether forms are > open, and if so then directly twiddling controls in those forms. > > I understand, and I support you in your not using classes. They are not > for everyone as several people have vociferously asserted. > > :) > > John W. Colby > www.ColbyConsulting.com > > > > On 6/22/2011 4:45 PM, Stuart McLachlan wrote: > >> Aha, someone else who gets it. :-) >> >> On 22 Jun 2011 at 14:26, Arthur Fuller wrote: >> >> I have followed JC's >>> threads and implemented them, but it is a lot of work, in several >>> different modules. >>> >> >> -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/**mailman/listinfo/accessd<http://databaseadvisors.com/mailman/listinfo/accessd> > > > Website: http://www.databaseadvisors.**com<http://www.databaseadvisors.com> > > >