Hi, I feel your pain :-) I had the same issue with Sybase Sometimes interpreting a null as '' :-(
I finally change the criteria to a custom column length(column) < 1 Ben Johansen - http://www.pcforge.com Authorized Witango Reseller http://www.pcforge.com/WitangoGoodies.htm Latest downloads & List Archives @ http://www.witango.ws -----Original Message----- From: [EMAIL PROTECTED] [mailto:owner-witango-talk@;witango.com] On Behalf Of Charles Brown Sent: Wednesday, November 06, 2002 5:10 PM To: Multiple recipients of list witango-talk Subject: Witango-Talk: <NULL> vs Blank The <NULL> vs just a blank field is not consistent in my MSSQL 2000 database. Sometmes it enters the <NULL>, sometimes not. This is causing a problem is a search action, which identifies the <NULL> and the "blank" as two seperate values, so I get two or more rows returned for the same individual. (My initial search brings back "unique" individuals meeting the search criteria. A drill down link is provided if the user wants to see all the activities associated with a particular individual. The drill down still works for individuals that are showing up more than once, but it is annoying to me and disconcerting to the users.) Suggestions will be greatly appreciated. ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
