I/O Error in a New Database

Question

I built a brand new AW database last week, and started populating it this week. I got 60 or so records in, then problems started. When I try to add a new record, AW crashes with "an I/O error occurred". This is NOT converting an old ClarisWorks file (I see that is a common error with those files). This is a brand new AW 6.2.9 DB.
I suspect I have to do the "save the current DB as .txt, create a new DB, then insert the old data" trick. But if I don't have to that would be preferred, since I designed some pretty nice layouts and don't wish to lose them.
Suggestions?

Answer 1

Hello
Just a "detail", for years, AW's spreadsheets where highly prone to corruption.
the anomaly was cured only when Apple introduced AW 628/629.
As Peggy wrote, the list view has nothing to do with a spreadsheet.
Why are database prone to corruption ?
Maybe simply because a single handler contain a wrong pointer calculation.
This was the origin of the SS anomaly, some other error of this kind would be sufficient to kill a DB.
In fact, I am using databases for years and got corruption only with DB containing multimedia fields. it's perhaps in the code dealing with this kind of fields that the anomaly is written.
But now it's no longer a problem as it will certainly not will be cured (except if some third party guy was able to find it and kill it).
My two pence for that:
REWARD: kill the DB corruption bug !!!
Yvan KOENIG (from FRANCE samedi 4 février 2006 21:04:10)