HP3000-L Archives

May 2000, Week 3

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:
Patrick Santucci <[log in to unmask]>
Reply To:
Patrick Santucci <[log in to unmask]>
Date:
Wed, 17 May 2000 16:55:19 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (26 lines)
On Tue, 16 May 2000 15:49:06 -0700, Mark Bixby <[log in to unmask]> wrote:

>Multiple people have replied privately to me saying they've had strong
>needs for their e3000 to become an ODBC client to talk to external
>non-e3000 databases such as Oracle or Sybase or MS SQL Server.
>
>Seems like e3000 ODBC client capabilities would be a valuable tool for
>enterprise and Internet interoperability....

Does it have to be ODBC? What about the middleware solutions from LeeTech
software? Check out <http://www.LeeTech.com/db-web/dbframes.htm>. They use
messaging to accomplish basically the same thing.

We looked at it about a year ago when we wanted to use ODBC or the
equivalent to have our 3000's query and update an Informix database on a
9000. It looked pretty good, and they even sent us a free demo. The only
reason we didn't go with it is that our number of transactions was so small
(under 100/day) we couldn't justify the cost. But if you want to, say,
update and/or replicate data from an SQL db on NT to/from an HP3000, I'm
pretty sure this stuff can do it. And although the examples they give
usually use the 3000 as the server, it can also act as the client (part of
our demo was client software for the 3000).

Just a thought,
Patrick

ATOM RSS1 RSS2