Remember Al Berry's comment about a column that allows nulls is poor design? In the case of addr1 and addr2, you could always further normalize the table, since it's any obvious 1 to many relationship, and have a table for address lines, no nulls necessary. (he he. Just trying to start a little design war.)
Actually, I now store addresses in VARCHAR columns, with the cr/lf embedded, if necessary. No nulls that way, either, unless the address is truly "unknown." Bill On Wed, 24 Jul 2002 15:44:08 -0400, Thomas J Cimicato wrote: >I second that motion. A null address line should not be blank filled or set >to some value for value's sake. If the address is null, I can check for a >null value. ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
