Forgive me, but I think you are mixing up two alternatives:

"UNLOAD then LOAD" is not the same thing as "RELOAD" - although you should end up with the same thing (with an error-free database).

Nevertheless, using RELOAD a new database is created and the indexes rebuilt in one go, and, more often than not, I have retrieved data this way when others have failed. You will still see error messages but ignore them if the process will continue. (You can always go back to your original db.)

You would also expect different row counts if you delete rows during the course of using your data.

Obviously, it's up to you, but try it and see if you are truly missing anything in the new db.

Regards,
Alastair.



----- Original Message ----- From: "Paul InterlockInfo" <[email protected]>
To: "RBASE-L Mailing List" <[email protected]>
Sent: Wednesday, June 10, 2009 10:10 PM
Subject: [RBASE-L] - Re: Life in RScope


Nope, Unload, re-load would fail and I hate that part. The data is there,
but the pointers are out of sorts.

I have a PK column for instance and it is 1 to 11855 and in the middle is
missing 11202-11853 rows. BUT I can see them with RScope and rattle by the
rows.

So if I unload I only get 1-11201 and 11854 and 55.  Keep in mind a few
deletes here and there when counting up the numbers to add up to why in
RBase explorer it says 11,707 and yet when you open the table you only see
11,104 and yet 1-11855 doesn't add up to either number 11,707 or 11,104. I
spent 2 minutes looking at that wondering if I need more coffee.


Oh it also contains a note field so Auto Fix is out also.   ;(



But   hey,  thank you for the input.


Sincerely,
Paul








-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Alastair
Burr
Sent: Wednesday, June 10, 2009 4:54 PM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Re: Life in RScope

Paul,

Without knowing your whole problem - have you tried a simple RELOAD on a
COPY of the database?

In my experience this sort of problem often/usually gets corrected just by a

simple reload but - as always with db errors - make sure that you copy the 4

db files and use those to work on. Then, if there's further problems, you
always have the "original" problem to go back to.

Regards,
Alastair.




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



No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.339 / Virus Database: 270.12.60/2166 - Release Date: 06/09/09 18:08:00


Reply via email to