Just an update. I was able to restore ALL 603 rows with the help of Mr. Bernard Lis. We spent several hours in my office going over all the rows one at a time.
Things I learned during the process besides backing up etc.... not by fault my NAS blew up! ;( 1. Rscope does a great job. I used to use it years ago in DOS day and there are many improvements over the years. 2. You need a comfortable chair and two people on a table this large. We actually had to take breaks while the other continued. 3. When the Tables says there are x-many of rows, yep they are there to be recovered you just need the 'R'ight tools. Watch the previous-next-current pointers and moved to 0. OMG! you can go cross eyed doing this. 4. Patience and more. I called John and my screen was doing a jumping thing on the last row, you could use 'Last row' and then move up the screen and then try to go back down and it was the fault of the table and NOT Rscope. He assisted and assured me that it was MY table and not Rscope and he was correct 100%. This table was so bad and I am sure John has seen worse, but I actually had to take a screen capture and send it to him. At one point, half way/ middle on the table all of the rows had the same pointer address. Like hundreds of rows! We had fixed 150+ bad pointers and then we were looking for more when we found this. I would like to thank all those that sent suggestions, scripts etc... It was ALL very helpful. Sincerely, Paul
