Max Wanadoo
max.wanadoo at gmail.com
Mon Mar 30 09:29:02 CDT 2009
>the argument about what null is would disappear IOW it would be nullified Max -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Dan Waters Sent: 30 March 2009 15:12 To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] SERIOUSLY OT: Re: An Interesting question YES! I find that when I'm working with a customer group to develop an automated process, the trickiest source of misunderstanding is terminology. I typically ask everyone to be aware of this and describe any terminology they are using in discussion. I've had to rewrite a lot of code because of this. Dan -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin at Beach Access Software Sent: Monday, March 30, 2009 8:58 AM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] SERIOUSLY OT: Re: An Interesting question I find that most differences of opinion, arguments if you will, stem from the two sides using different definitions of the same word. In this case if each side will spell out their definition of NULL, the argument about what null is would disappear. You might end up with Null(1) and Null(2) but you'd have agreement. When I say Null(1) is... There could be no disagreement. Rocky Smolin Beach Access Software 858-259-4334 www.e-z-mrp.com www.bchacc.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com