John W. Colby
jwcolby at ColbyConsulting.com
Mon Jun 12 20:05:26 CDT 2006
LOL, I have to thank Lambert for taking my place at the podium. It's good to see that AccessD continues on (and on...) <grin> JWC -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of DWUTKA at marlow.com Sent: Monday, June 12, 2006 8:33 PM To: accessd at databaseadvisors.com Subject: Re: [AccessD] Class Rebuttal was: Basic Unbound Form ... Welcome to the AccessD world of Global Variable debate. The argument is that someone somewhere got a wild bug up where the sun don't shine over the MISUSE of a globally scoped variable. Because of that, they declared that ALL globally scoped variables are bad, and somehow people took it as law, instead of seeing that only misuse is bad practice. Kind of silly, eh? Drew -----Original Message----- From: Stuart McLachlan [mailto:stuart at lexacorp.com.pg] Sent: Monday, June 12, 2006 5:01 PM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Class Rebuttal was: Basic Unbound Form ... On 12 Jun 2006 at 16:50, Heenan, Lambert wrote: > What's unclean about a class member reading the INI file and storing > the connection string. Serving it all to the application when it needs it? > > MyConnectionStirng = globStrConnectionString > > Vs. > > MyConnectionString = MyClass.ConnectionString > What benefit does your alternative actually achieve in exchange for adding the complexity of defining MyClass? This looks to me like complexity for the sake of "political correctness". -- Stuart -- 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