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
- Witango-Talk: Unicode Brandano, Peter
- RE: Witango-Talk: Unicode Ben Johansen
- RE: Witango-Talk: Unicode Brandano, Peter
- RE: Witango-Talk: Unicode Ben Johansen
- RE: Witango-Talk: Unicode Brandano, Peter
- RE: Witango-Talk: <NULL> vs Blank Charles Brown
- RE: Witango-Talk: <NULL> vs Blank Ben Johansen
- Re: Witango-Talk: <NULL> vs Blank Stefan Gonick
- Re: Witango-Talk: <NULL> vs Blank Mike Tyranski
- Re: Witango-Talk: <NULL> vs Blank Charles Brown
- Re: Witango-Talk: Unicode Ed Edgar
- Witango-Talk: Amazon Web Services John Newsom
- Re: Witango-Talk: Amazon Web Services Scott Cadillac
- Re: Witango-Talk: Amazon Web Servic... John Newsom
