No.  All horror stories I've heard have all been op errors.

Users, don't you just love them?!

Then again, we don't allow write access with our
ODBC driver, so any potential horror stories are
thereby avoided.

There is an incompatability with some ODBC drivers
to understand Image arrays, but heck, Image arrays
are not "standard" SQL, so full compatability with
the Microsoft spec of ODBC is not to be expected.
I would think any user trying to force the issue is
on their own, although any HP3000 ODBC vendor has to
have a way of getting through this via their own
extensions to the Microsoft spec of ODBC.

For example:  One unnamed vendor can handle Image
arrays in their ODBC, but you can't index on any
of those arrayed fields.  (Not that I think any
other vendor could do it either, so I'm happy
as it is.)  Besides most Image databases will have
plenty of other non-arrayed fields to index on, so
it should be that critical an issue.

In another situation, the ODBC driver is not a problem,
and Third Party Indexing (TPI) is not a problem either.
But try and mix the two, and you "may" have problems.

Tracy M. Johnson
TRW Automotive Electronics
Sensors & Components


-----Original Message-----
From: Mike Moncrieff [mailto:[log in to unmask]]
Sent: Wednesday, April 12, 2000 3:43 PM
To: [log in to unmask]
Subject: ODBC


Anyone had good experiences, horror stories to tell about using the
available ODBC drivers for IMAGE

Mike Moncrieff