Valentina 2.5.6 problem

[Ruslan Zasukhin]

On 27/2/07 9:17 PM, "Brendan Murphy" <bmurf at comcast.net> wrote:

Hi Brendan,

* So you think something is broken in 2.5.6 ?
* you can reproduce this issue with segment from scratch db ?

Actually segment error is not related to index.


> As a follow up on my recent email, I did a little experimentation.
> Originally I had the database cache set to 20 MB and the
> application dies as shown below. I then bumped the database cache
> to 200 MB and the database was created and then opened correctly.
> So is there a problem if the data base exceeds the cache? I think
> this problem needs immediate attention and a fix put out ASAP.
> 
> I wrote:
>> I am using Valentina 2.5.6. I get the following error when trying
>> to read in a local database file.
>> 
>>> Error code = 628011
>>> Error message = Segment "1" is wrong. The last segment is "0".
>> 
>> When I diagnose it with Valentina Studio problems with index files
>> show up. Here is a sample from the diagnose.
>> 
>>> ==========> Field: docattribute_id , type Long
>>> ==========> IndexFile
>>> PAGE (0, 0) Inventory pages have wrong physical page
>>> number.Inventory pages have wrong sum of physical page
>>> numbers.Index Inventory pages CORRUPTED. Some big page is not
>>> marked as first.
>>> 
>>> Problems found!  ( IndexFile )
>> 
>> I had no problems when using a previous 2.x version of Valentina.
>> Is this a Valentina problem or is there something I need to update
>> in my code to be 2.5.6 compliant?

-- 
Best regards,

Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc

Valentina - Joining Worlds of Information
http://www.paradigmasoft.com

[I feel the need: the need for speed]