Paul after Glenn after me:

> > How is your database set up?  Specifically, do you have
> > *all* Master sets defined before *any* Detail?

> > ..... I tried it on a database that I know for a fact has
> > details 'interleaved' with masters.

> It created the B-trees for all the masters without issuing
> any error messages. .....

Paul, when you say "It created the B-trees" it makes me think
that you were doing a DBUTIL  ADDINDEX.  The problem I had
was in doing a  DROPINDEX,  on a database where the root
file still thinks the HFS index files should be there but they are
not.  It is the  DROPINDEX that fails without the "FORCED"
in front of the  <ALL | setnamelist | setnumlist>.  Adding the
"FORCED" parameter tells DBUTIL to go ahead and "drop"
the indexes regardless, even though the HFS files are already
gone.  But with the addition of "FORCED" you will then get an
IMAGE error on the first DETAIL you run in to, if you have done
a  DROPINDEX <database name> FOR FORCED ALL.  If all
your MASTERs do not all come before your DETAILs in the
set list, then you'll have to use the "setnamelist" or "setnumlist"
options.

Once the root file is "corrected" to reflect no B-Tree indexes,
then you can go ahead and do the usual  ADDINDEX without
any problem.  From your above, it sounds like that is the step
you were talking about....

:-)
Ken Sletten