Jennifer Downs writes:

>>> Jennifer Downs <[log in to unmask]> 10/09/98 09:14am
>>>
Hi!

I'm running Omnidex 3.04 indexing a date field on a dataset with
100,000+
records. TPI is set on. Every night, this date field is updated on
approximately 300 records with a canned program. The problem is that
the
field isn't indexing properly, so if I do a serial search on that field, I
get 300 records...if I do an Omnidex search, I get between 10-20
records.
There is no discernable pattern to the 10-20 that index properly. It looks
pretty random. Talking to a programmer friend, it was suggested that this
might be a Btree problem (I don't know what that means, but it sounds
pretty cool. <s>). Tech support for the canned ap is baffled. Any
thoughts
or suggestions on how to solve the problem? Right now I'm reindexing
every
night, which is not a good long term solution since it chops an hour out of
the available night processing time.
--------------------------------------------------------------------------------
I don't have any ideas of why your puts aren't working, but I have a
question about your "date" fields.  I can find no mechanism to call an
index a date in OMNIUTIL.  An implication of calling it a date would allow
Omnidex to possibly assume a century when storing the index allowing 6
character date retrievals when crossing the century to be done in one
DBFIND, DBGET loop sequence.  Do you know something I don't know?
Inquiring minds need to know.

Mike Berkowitz
Guess? Inc.