Thanks Karen. I rounded off a few values with numerous zeros after the decimal point and dropped a table that I added in the past week and the reload appeared to work fine with no errors.
Bill From: [email protected] [mailto:[email protected]] On Behalf Of Karen Tellef Sent: Thursday, September 24, 2015 9:26 AM To: Bill Niehaus Subject: [RBASE-L] - Re: RBase 9.5 64 bit corrupted database Hey Bill, I just had the same thing happen! And it appears to have happened with a particular 9.5 64-bit build, because the reload doesn't show an error in a previous build (I'd have to look which 2 I tried). But anyway, it was a case of rows that had a bunch of zeroes in a REAL datatype, like 0.0000005 or -0.00000005. In my case since I knew which table was the offender, I was able to easily match the PKs in the "before" with the "after", determined which rows were dropped and did an UPDATE command to set the column = 0 for those rows. Then I did another reload and it worked. I was thinking of doing an update where the column was between certain numeric values, but decided this was safer. Not sure about your second error Karen -----Original Message----- From: Bill Niehaus <[email protected]> To: karentellef <[email protected]> Sent: Thu, Sep 24, 2015 9:10 am Subject: [RBASE-L] - RBase 9.5 64 bit corrupted database A few of our procedures are returning unusual results, so we decided to reload the database. When we do the reload, we get about 8 errors saying that Stand1Dev must be a valid real. This is a column that is defined as REAL and has many 0 values or values from 90 to -90. (We get a few more errors for the column Disease6Dev saying must be a valid REAL). During the RELOAD we also get some errors that say : Column is not in the table tempfldwt (no column name is given). This table appears ok for the definition when we do LIST. We also get some errors Illegal column name (no column name is given). We get these messages even when we loaded structure1, then the data and then the structure2 file with ALTER TABLE command. Not sure what to try next. Thanks. Bill Niehaus
