In R:scope, the label in front of the address says "Next Block" therefore the next block cannot start at the address where the last block ends. So the next block has to start at one more than the end. Although this has worked for me for a long time, I always wondered if there was something else existing at that address that I might be clobbering, but I haven't had any bad experience using it that way. Perhaps Razzak can clarify. Where is he hiding? haven't seen any responses from him lately.
----- Original Message ----- From: "Alastair Burr" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, January 24, 2002 6:45 AM Subject: Re: Database Problems > > Using explorer or at the command prompt get the size of the .rb2 file. > > using R:scope, Fix structure for file 2 = db2size + 1 > > then do the checks again dbinfo, structure, tables. > > Bernie Lis > > Megabytes, Inc. > > > Bernard, do you know why this works? Obviously it's great for Phil that it > did but it doesn't seem to me to be a "good" way to solve the problem. (All > the same, I'm all for any way that works if nothing else does!) > > The topic of AUTOCHK giving a message that errors were reported at the end > but showing nothing against any table has come up on this list before > recently (a few months ago, approx) - which is what I read happened to Phil. > It has happened to me a few times and I believe that somebody said that it > was a result of an error in the index file (RB3). Previously, each time I > had resolved it by doing a reload except last time a few days ago when I > tried PACK INDEX - which also worked. > > Razzak, if this is true, is it possible, please, to have the error message > changed to indicate that RB3 contains errors? > > Regards, Alastair. > > > > ----- Original Message ----- > From: "Phil Nolette" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Thursday, January 24, 2002 5:40 AM > Subject: RE: Database Problems > > > > Bernard, > > You are the man! > > I made the change and had no earthly idea about the +1 and it accepted it. > > I went back into the database (skeptical) and did an autochk and no errors > > were found. The tables that were not accessible are now accessible. > > Thank you so very much! > > Phil > > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On > > Behalf Of Bernard Lis > > Sent: Wednesday, January 23, 2002 11:52 PM > > To: [EMAIL PROTECTED] > > Subject: Re: Database Problems > > > > > > Using explorer or at the command prompt get the size of the .rb2 file. > > using R:scope, Fix structure for file 2 = db2size + 1 > > then do the checks again dbinfo, structure, tables. > > Bernie Lis > > Megabytes, Inc. > > > > ----- Original Message ----- > > From: "Phil Nolette" <[EMAIL PROTECTED]> > > To: "Rbase-L (E-mail)" <[EMAIL PROTECTED]> > > Sent: Wednesday, January 23, 2002 10:04 PM > > Subject: Database Problems > > > > > > > I have a very large database that got corrupted. I am trying to get the > > > processed conversion data exported. I used to be able to see the data in > > the > > > converted table (browse) but now even that is gone. I called RBTI and > got > > > John and he sold me the "silver bullet" RSCOPE for $150. I ran that > > against > > > each of the tables but I still get the following message (-ERROR- Error > in > > > length of database file 2. (1227)). > > > - I received this message when I ran the AUTOCHK TEST_CD FULL command > > > from the R Prompt > > > - I ran RSCOPE on every data table and there were no errors. > > > > > > The information at the end of the full report says: > > > Database statistics: > > > > > > Table entries allocated: 51 Table entries in use: 50 > > > Table entry utilization 98.0392156862745% > > > > > > Column entries allocated: 700 Column entries in use: 623 > > > Column entry utilization 89.% > > > > > > Index entries allocated: 25 Index entries in use: 25 > > > Index entry utilization 100.% > > > > > > File #2 active space: 402049052 File #2 unusable space: 1745426404 > > > File #2 utilization 18.7219393300484% > > > > > > Errors have been encountered. > > > > > > If anyone has any ideas about the repair process, please reply or send > > them > > > to: [EMAIL PROTECTED] > > > > > > Thank You, > > > > > > Phil Nolette > > > > > > > > > ================================================ > > > TO SEE MESSAGE POSTING GUIDELINES: > > > Send a plain text email to [EMAIL PROTECTED] > > > In the message body, put just two words: INTRO rbase-l > > > ================================================ > > > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > > > In the message body, put just two words: UNSUBSCRIBE rbase-l > > > > ================================================ > > TO SEE MESSAGE POSTING GUIDELINES: > > Send a plain text email to [EMAIL PROTECTED] > > In the message body, put just two words: INTRO rbase-l > > ================================================ > > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > > In the message body, put just two words: UNSUBSCRIBE rbase-l > > > > > > ================================================ > > TO SEE MESSAGE POSTING GUIDELINES: > > Send a plain text email to [EMAIL PROTECTED] > > In the message body, put just two words: INTRO rbase-l > > ================================================ > > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > > In the message body, put just two words: UNSUBSCRIBE rbase-l > > ================================================ > TO SEE MESSAGE POSTING GUIDELINES: > Send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: INTRO rbase-l > ================================================ > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l
