Bruce, I recently encountered this myself. When I did a LIST tablename for the table where the error happened, the constraints looked correct. But when I went into Database Explorer table designer to look at the keys, one or more of the FK's had lost its default messages. I dropped those constraints, checked that the data would allow the FK constraint, and recreated the FK. The autochk error went away.
I have also seen an occasional error where the LIST CONSTRAINTS results would not show any table in the "referenced" column for a foreign key. I don't think Autochk gave the Error reading index list message then, but instead gave a message like 'referenced table not valid." Bill On Thu, Oct 7, 2010 at 12:14 PM, Bruce Chitiea <[email protected]>wrote: > Buddy; > > 'No indexes' is the expected result of LIST INDEX as I'm relying on the > implicit indexing of the PKs and FKs for now. > > LIST CONSTRAINT (thanks for the tip) shows all the PKs, FKs, PK > REFERENCEDs and NOT NULLs I expect to see. > > The "Error Reading the index list" result of AUTOCHK is the puzzler. > > I have R:Scope at another office. Is that my next stop? > > bruce chitiea > safesectors inc. > v8.0.23.30809 SU > > > -------- Original Message -------- > > Subject: [RBASE-L] - RE: AutoChk / Index Error > > From: "Walker, Buddy" <[email protected]> > > Date: Thu, October 07, 2010 8:45 am > > To: [email protected] (RBASE-L Mailing List) > > > > > > Bruce > > > > Maybe I missed something but I don't see where you are creating an > index. That is why when you "List INDEX" nothing is found. If you want to > see your PK and FK do "LIST CONSTRAINT" > > > > >
