HP3000-L Archives

June 1999, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Mark Bixby <[log in to unmask]>
Reply To:
Date:
Thu, 3 Jun 1999 09:59:36 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (24 lines)
claire Pope writes:
>
> We have Omnidex which can use third party indexing on our image databases.
> We now have it disabled.  Does anyone know of any problems we might encounter
> if we enable it?  I guess mainly I need to know if this is a 'dangerous'
> thing to do for some reason.

Using the standard TurboImage intrinsics to access Omnidex-ed data via TPI
works fine.

But if you don't *need* to do this, you don't gain anything by enabling TPI.

The only trouble we've had (and STILL have) with TPI is being unable to
re-attach an important production database to Image/SQL after we upgraded our
Omnidex version.  It appears to be an HP problem, yet the SR *STILL* hasn't
even been classified by the lab.  But this is a RANT for another posting when
I have the time to gather dates and HPRC call IDs......
--
Mark Bixby                      E-mail: [log in to unmask]
Coast Community College Dist.   Web: http://www.cccd.edu/~markb/
District Information Services   1370 Adams Ave, Costa Mesa, CA, USA 92626-5429
Technical Support               Voice: +1 714 438-4647
"You can tune a file system, but you can't tune a fish." - tunefs(1M)

ATOM RSS1 RSS2