-----Original Message-----
From: Doug Greenup [mailto:[log in to unmask]]
Sent: Thursday, May 16, 2002 3:45 PM
To: [log in to unmask]
Subject: Re: Fwd: [HP3000-L] Giving up...


Hi Braun:

Minisoft produces an ODBC and JDBC driver for the HP3000.  We have close to
2,800 HP3000's using our ODBC driver everyday to develop web applications,
to develop client/server applications, and to do reporting.  Many of these
customers also use our JDBC driver (now 3.0 compliant) quite successfully.
We have added HP Eloquence support to our drivers and will soon be
releasing support for Oracle making our drivers tools for migration to Unix
or NT.  We are not "free" but are reasonably priced and WORK.  More
information on our drivers is available from www.minisoft.com.

Thanks for your time,

Doug Greenup
Minisoft, Inc.

ODBC/32 is indeed inexpensive and for the most part works as advertised.

I have a few issues with it though:

The Schema editor is extremely difficult to work in if you need to define
your own layout. It does a good job at reading various self described files
and databases, but can be very annoying if you need to lay out a flat file.
I generally find it easier to create a PowerHouse dictionary for the file
and have the editor extract the format from it.

Also be aware that the Minisoft driver opens every file in the DSN when you
connect and does not release them until you disconnect. If any file listed
in the DSN does not exist, or if there is any kind of open error, you cannot
access any other file. Minisoft's recommended solution has been to create
multiple DSN's which of course means multiple connections to retrieve your
data.

And if you use an Omnidex indexe it must be the first item in the WHERE
clause or the driver will not use it as an Omnidex key. This can lead to
inconsistant resuts when using multiple key indexes as a search using the
key for the word "CONTRACT" will return any record that has that word in the
key. But if the key is not used, only records where the field is exactly
"CONTRACT" will be returned. So keep tight control on your maintenace of the
WHERE clause.

Comments are my own... not my employer's... etc.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *