I have had a few cases were the index function failed to update the table correctly. An index on a datefield reported new records on 18 days instead of 20. This malfunction was easily detected but what worrys me a lot is when we have index on fields where malfunction is not as obvious. Is there a way to verify a correct index function? In the case with weekdays new records where correctly updated, so we didn't realized the problem until the monthly report lacked records.

Thanks

Bertil

Were the index transactions there and not getting flushed?

The Sprezzatura Group

World Leaders in all things RevSoft

Bertil,

Define the key structure for this table. There are known problems with index flushes with OI32. They are obscure, but there nonetheless.

[email protected]

SRP Computer Solutions, Inc.

Hi

The problem I described just occured and I tried to update index but that did not change anything, the dict key is proberly defined as far as I understand, any idea?

Thanks

Bertil

Bertil,

I'm sure your dictionary structure is defined correctly. The problem I'm describing happens to particular keys, whether or not they are defined correctly. Is this a multi-part key? Do your keys have trailing zeros in them? Are you using the latest V119 patch?

[email protected]

SRP Computer Solutions, Inc.

Do your keys have trailing zeros in them?

I meant, "Do your keys have preceeding[/i] zeros in them?" [email protected] SRP Computer Solutions, Inc. </QUOTE> —- === At 26 AUG 2003 02:35AM Bertil Strom wrote: === <QUOTE>Sorry I don't know how to check it, what I did was using the update function, but that didn't help. Bertil </QUOTE> —- === At 26 AUG 2003 09:44AM Bertil Strom wrote: === <QUOTE>My keys are 2 part. Part 1 is integer and part 2 is varchar Rebuild fix the problem but am happy for a better solution. Bertil </QUOTE> View this thread on the Works forum...