Re: New DB2/400 Drivers Officially Released from Microsoft...

[Steve Richter <stephenrichter@xxxxxxxxx>]

On 11/10/05, pnelson@xxxxxxxxxx <pnelson@xxxxxxxxxx> wrote:
> What is the point of a DB driver
> that can only be used on a server system?
>
> Um, because M$ wants to push Wintel servers?

competition is good. companies that are stagnant, that want to get by
with a minimum of investment and risk, like IBM and GM, decline.  Why
be loyal to a company that has decided to invest zero dollars in the
native side of its own system?

-Steve

> --
>
> Paul Nelson
> Arbor Solutions, Inc.
> 708-670-6978  Cell
> pnelson@xxxxxxxxxx
>
>
>
>
> Steve Richter <stephenrichter@xxxxxxxxx>
> Sent by: midrange-l-bounces@xxxxxxxxxxxx
> 11/10/2005 06:47 AM
> Please respond to
> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
>
>
> To
> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> cc
>
> Subject
> Re: New DB2/400 Drivers Officially Released from Microsoft...
>
>
>
>
>
>
> On 11/9/05, richard@xxxxxxxxxxx <richard@xxxxxxxxxxx> wrote:
> > Apparently this driver requires SQL Server 2005 as well.   I just tried
> to
> > install it.
>
> I saw that also.  I dont follow.  What is the point of a DB driver
> that can only be used on a server system?  Using sql server to connect
> to another database seems similar to having server side cursors ...
> ado.net discourages the use of server side cursors.
>
> -Steve
>
>
> >
> > Not useful in a client environment unless it can be installed without
> SQL
> > Server 2005.
> >
> > If I missed something, please let me know.
> >
> > Regards,
> > Richard Schoen
> > RJS Software Systems Inc.
> > "Providing Your....iNFORMATION NOW!"
> > Email: richard@xxxxxxxxxxxxxxx
> > Web Site: http://www.rjssoftware.com
> > Tel: (952) 898-3038
> > Fax: (952) 898-1781
> > Toll Free: (888) RJSSOFT
> > ------------------------------
> >
> > message: 5
> > date: Wed, 9 Nov 2005 11:31:19 -0800
> > from: "David Delisi" <daviddel@xxxxxxxxxxxxx>
> > subject: New DB2/400 Drivers Officially Released from Microsoft...
> >
> > On Monday, Microsoft announced new drivers for DB2/400 as part of the
> > Visual Studio 2005 product launch.
> >
> >
> >
> > The OLE DB Driver for DB2 supports connectivity over TCP/IP and can be
> > considered a replacement for IBM Client Access. In this scenario, the
> > customer does NOT need to license Microsoft Host Integration Server 2004
> > which is how the drivers were traditionally distributed.  As always,
> > test your applications before replacing any other technology to ensure
> > 100% compatibility.  The drives are a free download.
> >
> >
> >
> > The driver supports IBM DB2 for OS/400 V5R1 and later to support an SNA
> > LU6.2 or TCP/IP network connection.
> >
> >
> >
> > Here is the link:
> >
> > http://www.microsoft.com/downloads/details.aspx?familyid=D09C1D60-A13C-4
> > 479-9B91-9E8B9D835CDC&displaylang=en
> > --
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.
> >
> >
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>