MOST Excellent. Thanks guys. That cleans up three tables... On Fri, Jul 18, 2008 at 2:16 PM, Bill Downall <[EMAIL PROTECTED]> wrote: > John, > > If there are columns with null values, they are not considered to match > other rows, even if those other rows also have nulls in those columns. This > is an SQL standards issue, in that NULLS cannot be compared for equality, > since they are by definition unknown. > > You can override this SQL setting in R:BASE, if you SET EQNULL ON just > before you run your DELETE DUPLICATE command. Don't forget to set it back to > OFF. > > Bill > > > On Fri, Jul 18, 2008 at 2:20 PM, John Croson <[EMAIL PROTECTED]> wrote: >> >> I'm noticing a bizarre behavior when I issue the DELETE DUPILICATE >> with no column references. >> >> Where there should clearly be a match, the rows are not deleted. Any >> ideas? >> >> BTW, I've compared rows of data by hand, and have found duplicate >> information in each field, so I know I'm not going batty...YET. >> >> -- >> John Croson >> [EMAIL PROTECTED] >> http://pcnorb.blogspot.com/ >> http://pcnorb.homelinux.org/ >> >> > >
-- John Croson [EMAIL PROTECTED] http://pcnorb.blogspot.com/ http://pcnorb.homelinux.org/
