jan@nprdc.arpa (Jan Dickieson) (07/28/89)
I have an application written in Knowledgeman/2 Version 2.5
distributed by MDBS. For those of you who have used the
software, you know it is very powerful. I have used it for the
last three years and this is the first instance where I've come
up against something that I can't resolve.
The application uses several tables. One of which has six
indexes:
INVOICE
ascending MANU descending INVOICE
ONCNST
ascending CNUMBER ascending PSTYLE
OCNUM
ascending CNUMBER
VDATE
ascending TOJUL(VDATE)
PAID
ascending TOJUL(PAID)
RECARD
ascending CNUMBER descending TOJUL(VDATE)
The associated fields have the following characteristics:
MANU STR 1
INVOICE NUM USING "dddddd"
CNUMBER NUM USING "dddddd"
PSTYLE STR 3
VDATE STR 8 USING "dd/dd/dd"
PAID STR 8 USING "dd/dd/dd"
The application has been running for almost a year now. The
most recent changes have involved the creation of the INVOICE
and RECARD indexes.
The problem is this . . . under some circumstances, the indexes
do not get updated, in fact, they get scrambled.
I have put in debugging to verify that:
1) there is enough memory (approx 178K bytes)
2) e.inup = true
3) all spelling is correct
4) e.serr = false
The software has absolutely NO idea that the indexes get messed
up. When I rebuild them, using the INDEX command, everything
gets straightened out.
If anyone can shed light on the problem I would greatly
appreciate it. It takes 45 minutes to rebuild indexes.
Thanks.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Jan Dickieson
Navy Personnel Research and Development Center
Code 141
San Diego, CA 92152-6800
(619) 553-7838
jan@nprdc.navy.mil