[AccessD] Class costs & benefits

Rocky Smolin at Beach Access Software rockysmolin at bchacc.com
Wed Feb 25 10:39:30 CST 2009


He brings the woodshed with him??!! 


Rocky Smolin
Beach Access Software
858-259-4334
www.e-z-mrp.com
www.bchacc.com
 
 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte Foust
Sent: Wednesday, February 25, 2009 8:35 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Class costs & benefits

>>I get the feeling sometimes that a lot of people don't respond because
they are afraid I might take them to the woodshed.

Really?  I thought it was to avoid the two by four you're carrying!  LOL

Charlotte Foust 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
Sent: Wednesday, February 25, 2009 8:30 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Class costs & benefits

William,

 > "In fact I will promise to not respond to any message unless the author
specifically asks me to for some reason."

I just want people to know that I have committed to not "jumping on" any
opinion.  I will not click "reply" on a post unless the author somehow asks
a question... "what about", "why not", "how do I", whatever.

I get the feeling sometimes that a lot of people don't respond because they
are afraid I might take them to the woodshed.

 >...beyond that unique trait I'm not yet sold on the "classes everywhere"
model you espouse ...still waiting for that magic bullet in your discourse
:)

I don't use "classes everywhere".  In my applications, and even in my
framework, there are about 60 / 40 classes to modules.

John W. Colby
www.ColbyConsulting.com


William Hindman wrote:
> "In fact I will promise to not respond to any message unless the 
> author specifically asks me to for some reason." jc
> 
> ...oh come on! ...I'm not begging you to respond to any message ...I 
> hope that you will but that's your choice ...you're being a PITA about

> this, eh ...you rant, we rant ...that's what makes AccessD better than

> any other list.
> 
> ...as for classes, I'm still learning but not yet committed ...in some

> simple cases so far I've seen advantages in code encapsulation but 
> nothing that I couldn't achieve otherwise ...but classes let me create

> and raise events outside the cbf ...that certainly has benefits 
> ...beyond that unique trait I'm not yet sold on the "classes
everywhere"
> model you espouse ...still waiting for that magic bullet in your 
> discourse
> :)
> 
> William
> 
> --------------------------------------------------
> From: "jwcolby" <jwcolby at colbyconsulting.com>
> Sent: Wednesday, February 25, 2009 10:47 AM
> To: "Access Developers discussion and problem solving" 
> <accessd at databaseadvisors.com>
> Subject: [AccessD] Class costs & benefits
> 
>> From Rocky's email I thought that perhaps a thread on what the costs 
>> and benefits are for classes.
>>
>> Jim made a statement that he felt that "Access has no implementation 
>> inheritance and since inheritance really is the whole point of using 
>> classes, I think they are more or less a waste in Access".
>>
>> So what are your feelings and opinions about classes?
>>
>> I will promise to treat every opinion as valid and not go into rant
mode. 
>> ;)
>>
>> In fact I will promise to not respond to any message unless the 
>> author specifically asks me to for some reason.
>>
>> --
>> John W. Colby
>> 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




More information about the AccessD mailing list