Re: IIS to as/400 odbc -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: IIS to as/400 odbc
From: "Leif Svalgaard" <leif@xxxxxxxx>
Date: Wed, 15 Aug 2001 11:02:21 -0500
List-Archive: <http://archive.midrange.com/midrange-l/>
List-Help: <mailto:midrange-l-request@midrange.com?subject=help>
List-Id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-Post: <mailto:midrange-l@midrange.com>
List-Subscribe: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=subscribe>
List-Unsubscribe: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=unsubscribe>

From: Joe Pluta <joepluta@PlutaBrothers.com>

> Walden, I wrapper all of my communications in objects, so the details are
> never exposed to "front end" programmers anyway.  hat's inconsistent.
>
> However, if you're highly vested in ODBC and your architecture is unlayered
> and you don't wrapper your server requests and your programmers are
> inflexible and your management is clueless, then sure, ODBC is the way to
> go.


That is a good description of the 'average' shop.

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.