corrupted indexing

[Claudius Sailer]

Hi Liz,

Am Samstag, 01.02.03 um 01:55 Uhr schrieb Elizabeth Robar:

> Woah... is this (corrupted indexing) a common situation?  I'm 
> developing right now for a product that will (hopefully) be in the 
> hands of hundreds of students within 6 months, and I can't have the 
> database not performing searches properly, due to indexing problems.  
> Because of the wide distribution, I wanted everything in one file, but 
> if this is a serious problem, I'll do it in multiple files.  For the 
> next year or so, users should only have one database; down the line 
> there will be multiple ones.

I know how I have to handle my application but I also know that users 
are not doing the same. The kill the application during an 
SQL-Statement or stop the application anyway which is not correct or 
okay, In this cases I wanted to have a easy way to fix problems with 
the database. So when there is a misstreating of the database or 
application it could be that the index is corrupt and RB-Appliction 
crashes with a Nil-Object-Expection --> not a fine application result.

With this experiences I decided to make 2 files.

There is not a bug or failure in V4RB it is a wrong handling of the 
user which I want to caught with this 2 files way. When I open the 
database the Database creates automatically an Index-file when there is 
no. So this is no problem when the indexfile is not there when you open 
the database :-))

bye


Claudius