Also, before you use the COUNT(*) syntax, remove the PK (or project the table). The COUNT(*) select will use the index not the data.

George H Baker wrote:
Tom,
Try R:Scope to take a look at the table involved. The problem may present itself as to location when a table check is ran. George

    ----- Original Message -----
    *From:* TOM HART <mailto:[EMAIL PROTECTED]>
    *To:* RBASE-L Mailing List <mailto:[email protected]>
    *Sent:* Sunday, August 31, 2008 9:10 AM
    *Subject:* [RBASE-L] - Re: Unique value

    Yes there was about 10k rows less before the reload.

    Tom



    ----- Original Message ----
    From: Emmitt Dove <[EMAIL PROTECTED]
    <mailto:[EMAIL PROTECTED]>>
    To: RBASE-L Mailing List <[email protected]
    <mailto:[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


--- RBASE-L
================================================
TO POST A MESSAGE TO ALL MEMBERS:
Send a plain text email to [email protected]

(Don't use any of these words as your Subject:
INTRO, SUBSCRIBE, UNSUBSCRIBE, SEARCH,
REMOVE, SUSPEND, RESUME, DIGEST, RESEND, HELP)
================================================
TO SEE MESSAGE POSTING GUIDELINES:
Send a plain text email to [email protected]
In the message SUBJECT, put just one word: INTRO
================================================
TO UNSUBSCRIBE: Send a plain text email to [email protected]
In the message SUBJECT, put just one word: UNSUBSCRIBE
================================================
TO SEARCH ARCHIVES:
Send a plain text email to [email protected]
In the message SUBJECT, put just one word: SEARCH-n
(where n is the number of days). In the message body, place any text to search for.
================================================


Reply via email to