Dennis

With the last corruption we did
Edit all from Table 
and went to the last row   # 8645
Actual count 8666  expected 7645

I thought Edit all from Table would take you to the last row and not use 
Indexes?  or do I have something backwards in my brain?

Thanks for all the help... 
Marc




 
 


--------------------------------------------------------------------------------

From: [email protected] [mailto:[email protected]] On Behalf Of MDRD
Sent: Thursday, August 19, 2010 2:58 PM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Re: Corrupt DB

 

Dennis

 

I checked the indexes and here they are

 --- ------------------ ------------------------------------------------------
   1 custnum            Type   : INTEGER  NOT NULL                            
                        Consrnt: FOREIGN KEY REFERENCES PTINFO                
                        Consrnt: UNIQUE                                       
   2 Date_con           Type   : DATE                                         
   3 TxDate             Type   : DATE     NOT NULL                            
                        Consrnt: UNIQUE                                       
   4 Treat_dr           Type   : TEXT 2                                       
                        Consrnt: FOREIGN KEY REFERENCES DRINFO                

 

 

This is the error

  Examining data in TravCard  Rows:  Active 7541, Deleted 0

Actual rows counted: 7543, expected count: 7541

-ERROR- The number of rows counted was not expected. (1254)

 

Thanks

Marc

 

 

From: Dennis McGrath 

Sent: Thursday, August 19, 2010 2:43 PM

To: RBASE-L Mailing List 

Subject: [RBASE-L] - Re: Corrupt DB

 

It could be that is that is the only table that user hits frequently.

 

Network connection is high on the list of causes, card or cable.

 

One other issue to check, the indexes on that table.

Are there any indexes that are highly inefficient, i.e. one value predominates, 
like NULL?

If so get rid of the bad index(es)

 

I had one client that required a rebuild of the db on a regular basis because 
it kept getting corrupted.

Eliminated a bad index and I haven't had to fix it for years!!!! 

 

Dennis McGrath

 


--------------------------------------------------------------------------------

From: [email protected] [mailto:[email protected]] On Behalf Of 
[email protected]
Sent: Thursday, August 19, 2010 1:17 PM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Re: Corrupt DB

 

Is the corruption always happening in the same table?  If it is, then it is 
hard to make a case that it's something hardware or network related...

Karen

Reply via email to