William: Make sure you backup the database before you do any work!!! Javier,
Javier Valencia, PE President Valencia Technology Group, L.L.C. 14315 S. Twilight Ln, Suite #14 Olathe, Kansas 66962-4578 Office (913)829-0888 Fax (913)649-2904 Cell (913)915-3137 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of William Stacy Sent: Wednesday, September 24, 2003 11:01 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Possible file corruption If you can access the R:> prompt, use the reload command to build a new copy of the database (to a different directory), then autochk that new copy and if ok, copy it over the corrupted copy. Craig Cohernour wrote: >Applogies if this appears twice. My last post >reported a rather vague error so I thought it >best to try again.... > >Pertinent info: > >* Windows 98se >* RBASE 6.1a >* Newbie to the group (and I'm not an RBASE > programmer ... yet. I do work with several > other languages/development environments so, > I'm sure I'll learn fast.) >* Have inherited a legacy application to support > and original programmer is not available for > assistance. > >Well, here goes. > >The system actually seems to run ok but when >running an "Integrity Scan" (menu item of system) >here's what I'm getting: > >----------------------------- >-ERROR- a row of data's length is too large >-ERROR- a row of data's previous pointer is out of range >-ERROR- a row of data's previous pointer is invalid >-ERROR- a row of data's next pointer is out of range > >The last address encountered was not expected >The number of rows counted was not expected > >AUTOCHK found errors in the database > >----------------------------- >DBERROR.LOG states that the errors are >occurring in a (virtual?) table called >SYS_REPORTS. (Please forgive me if I don't >have all the terminology correct.) >----------------------------- > >Examining data in file #2... > Examining data in SYS_COMMENTS Rows: Active 399, Deleted 0 > .bla > .bla > .bla > Examining data in SYS_COLUMNS > Examining data in SYS_INDEXES > Examining data in SYS_FORMS Rows: Active 2076, Deleted 0 > Examining data in SYS_REPORTS > >-ERROR- A row of data's length is too large. >-ERROR- A row of data's previous pointer is out of range. >-ERROR- A row of data's previous pointer is invalid. >-ERROR- A row of data's next pointer is out of range. > > Rows: Active 7502, Deleted 0 >-ERROR- The last address encountered was not expected. >Actual rows counted: 9397, expected count: 7502 >-ERROR- The number of rows counted was not expected. > Examining data in SYS_LABELS Rows: Active 957, Deleted 0 > Examining data in SYS_LAYOUTS Rows: Active 77, Deleted 0 > >.... bla bla bla > >Database statistics: > > Table entries allocated: 71 Table entries in use: 71 > Table entry utilization 100.% > > Column entries allocated: 566 Column entries in use: 566 > Column entry utilization 100.% > > Index entries allocated: 54 Index entries in use: 54 > Index entry utilization 100.% > > File #2 active space: 1482752 File #2 unusable space: 327680 > File #2 utilization 81.9004524886878% > >Errors have been encountered. > >----------------- > >Of course, I'm not asking anyone to support the >data system here... just clue me in as to what >may be wrong, guide me on what I may be able to >do to correct the problem, etc. Any help/guidance >is greatly appreciated. > >Please forgive the long post. > >Thanks in advance. > >- Craig > >. > > >
