V4RB - DEFRAGMENT after deletion of records

[RB User]

On 9/25/05 3:45 AM, "Ruslan Zasukhin" <sunshine at public.kherson.ua> wrote:

>> I tried closing the DB between the delete operation and the defragment, but
>> it didn't help.  After performing the defrag, the DB wouldn't open (threw
>> the usual -39 error).
>> 
>> Diagnose says everything is ok, unless I perform the delete and the defrag
>> on the same DB.  If I perform both operations on the same DB, the DB becomes
>> unusable after the defrag, and I can't run Diagnose.
> 
>>> So you use 1.10 ?
>>> Even not 1.11 ?
>> 
>> I have upgraded to 1.11 today, but the problem persists.
>> 
>> After experimenting today, I've discovered that the problem does not occur
>> if I only delete a few records from the table INSTEAD of all the records in
>> the table.  I can delete a few records, then defrag, and the DB stays
>> usable.
>> 
>> But if I delete ALL the records in the table, and then defrag, the DB
>> becomes unusable.
> 
> Very strange. It seems many people have use Defragment long time, nobody
> complains on this.
> 

Yes!  Works wonderfully, unless I delete all the records in the table!

Let me check and see if the problem goes away with 2.X.  Perhaps this is
just Fate telling me I should've already migrated this project to 2.x. :-)

> 
>> Unrelated side note: Is the V4RB 2.0.5 download for Mac OS X not working? I
>> think the installer is missing something.  I get an error when I try to run
>> it. I wanted to see if this current problem goes away with 2.0.5. (Ruslan, I
>> also promised you earlier this month I would check and see if the aggregate
>> function permissions issue went away with 2.0.5, but I haven't had time
>> yet!)
> 
> 2.0.5 do works, several RB developers have confirm this on beta list.
> 

Forgive me, I was committing a blunder during the install.

> What OS you use ?

OS X.3.9.

Russ