Not if the pointer is off and pointing to the wrong range and that other row is in that range.
Example from RScope: (I hope it kind of better explains the problem) ERROR Changes made to a NOTE column in table clients have caused this row to be relocated lower in the table. The location of the new row is 0 and it should be within the range of 29278209 to 29278209. ERROR The pointer to the previous row of data in table clients is set to 0. It should be within the range of 0 to 28269109. ERROR The number of rows counted for table clients was 3591. The structure file expects to count 3592 rows. 3 Errors Rows: Active 3591, Deleted 0 File2 active space: 4030464 File2 unusable space: 0 File2 utilization 100% 3 errors found for the selected tables This is an example from a 7.6 RScope months/years back. But as you can see the pointers are pointing to the wrong range. Once fixed the data is there. Just temp lost. Paul From: [email protected] [mailto:[email protected]] On Behalf Of MDRD Sent: Saturday, August 21, 2010 12:51 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Corrupt DB 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 <mailto:[email protected]> Sent: Thursday, August 19, 2010 2:43 PM To: RBASE-L Mailing List <mailto:[email protected]> 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
