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:
Mark Bixby <[log in to unmask]>
Reply To:
Mark Bixby <[log in to unmask]>
Date:
Wed, 17 May 2000 14:11:47 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (24 lines)
Patrick Santucci wrote:
>
> 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.

In my particular case of Perl and PHP, yes, it needs to be ODBC in order to
take advantage of the ODBC capabilities already built in to Perl and PHP.

I would like to see the e3000 versions of Perl and PHP someday be able to talk
to databases both on the e3000 and externally.  ODBC would be a quick & easy
way of doing that.

- Mark B.

ATOM RSS1 RSS2