Re: CDX index corruption?

Bert

After im****ting your data the index may be *unbalanced* and re-creating
them 
causes a rebuild of the internal tree (to become *balanced*).

A couple of things:-
    Why are you using Clipper syntax when you have a Server defined??
    Why are you using 2 index files instead of 2 TAGS (ie 1 index file)??

By using a single index file (with TAGS) you have no need to use the 
Setindex() method/function.

If you use a Server there is NO NEED to use CLIPPER syntax at all
I suggest you forget the DB?? functions even exist in VO

> DBCREATEINDEX("Ing_IngNr","INGRNR",{||INGREDIENT->INGRNR})
> DBCREATEINDEX("Ing_Ingred","INGREDIENT",{||INGREDIENT->INGREDIENT})
Don't use the ALIAS as part of your index expression, there is no
guarantee 
that the server will use that alias when you open it (definately won't be
if 
you open it more than once in the same app).

> I made sure that I delete the index files before building the index,
like 
> I read in this NG.
The reason for that is:
If you recreate the indices/TAGS without first deleting the file(s) the
old 
*TAG* is marked as obselete and the new one APPENDED to the end of the
file 
and set as the active one. (it's called index bloat) (even though your not

using TAGS the effect is still the same)

CYA
Steve