Mark Bixby writes:

>>> Mark Bixby <[log in to unmask]> 11/18/97 09:55am >>>
Ever since we upgraded from Omnidex 3.03.20 to 3.04.50 about a month
ago, we've
been having problems with our TPI-enabled databases:

1) Image/SQL wouldn't recognize Omnidex keys when ATTACHing these
TPI-enabled
database to a DBE.  This has been solved by upgrading to a more current
version
of Image/SQL.

< rest snipped >

I have open support calls with both the HPRC and DISC about these
issues.
Since we're approaching the one month anniversary of this problem, I
thought
I'd ask on HP3000-L if any other Omnidex users are on 3.04.50, and
whether or
not you've been having problems.  Feel free to reply by private e-mail if
you prefer.  Thanks.
--------------------------------------------------------------------------------------
We had the same problem, only in reverse.  We've been on the version
3.04.10 of Omnidex and G.00.13 of Image/SQL.  We wanted to upgrade
to G.00.14 and Omnidex came back and said it couldn't re-register the
indexes when when did a split in Imagesql.  It turns out that we need to
go to Omnidex 3.04.50 to fix this.  I think HP, DISC and Bradmark need to
get together to determine compatible versions and publish them in the
communicator and in patch documentation.  They are too tightly
integrated to be treated as separate products.

Mike Berkowitz
Guess? Inc.