HP3000-L Archives

November 1997, 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:
Wed, 5 Nov 1997 11:21:31 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (28 lines)
I have the Express 3 powerpatch tape in my hot little hands.  :-)

The Communicator is sort of vague about whether or not:

1) The HPPCAPI ODBC clients we have installed throughout our user base will
still be able to communicate with our 3000 once I install Express 3?  It will
be a while before we have time to install ODBCLink/SE on our PC clients.

2) Is running HPPCAPI on the client side still officially supported by HP under
5.5 Express3?

Also, the end of the Communicator article about ODBCLink/SE lists several
features *not* included in the FOS SE version, but which are included in the
full-blown ODBCLink product from MB Foster, particularly "Support for TPI
keyword indexes used by Omnidex and Superdex".  ????  I'm confused;  I thought
TPI support was a function of HP's Image/SQL, not ODBCLink.  We have an
important production application using the HPPCAPI ODBC client to access an
Image/SQL DBE attached to a TurboImage database with Omnidex TPI keys.  We'll
be rather upset if this won't work after I install Express 3.....

Can anybody clarify this for me?
--
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               +1 714 438-4647
"You can tune a file system, but you can't tune a fish." - tunefs(1M)

ATOM RSS1 RSS2