Yes there was about 10k rows less before the reload. Tom
----- Original Message ---- From: Emmitt Dove <[EMAIL PROTECTED]> To: RBASE-L Mailing List <[email protected]> Sent: Sunday, August 31, 2008 7:17:18 AM Subject: [RBASE-L] - Re: Unique value Tom, That is likely because the RELOAD removed the offending row. Can you look at a row count just prior to and just after the RELOAD? Emmitt Dove Manager, DairyPak Business Systems Evergreen Packaging, Inc. [EMAIL PROTECTED] [EMAIL PROTECTED] (203) 643-8022 From:[email protected] [mailto:[EMAIL PROTECTED] On Behalf Of TOM HART Sent: Saturday, August 30, 2008 10:34 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Unique value Just tried that and said no rows satisfy where clause. Tom ----- Original Message ---- From: Ben Petersen <[EMAIL PROTECTED]> To: RBASE-L Mailing List <[email protected]> Sent: Saturday, August 30, 2008 9:17:57 PM Subject: [RBASE-L] - Re: Unique value Hi Tom, You could: Select colName, count(*) from tblName group by colName having count(*) > 1 Ben TOM HART wrote: I have a table that has a PK and everything works fine but today I was doing some maintenance and did a reload, when it got to reloading the suspect table I get the error that it must contain a unique value. If I do an autochk it does not show any errors. So two questions: 1. What happened, and 2. How do I find the culprit in 85K rows. Tom Hart
