RE: SQL views

Well, if you need to drive a nail, do you dig some iron ore in Minnesota,
transport it to Pennsylvania to be turned into steel, and then travel to
Stanley Tools forge in Connecticut to have it turned into a hammer, or do
you just go buy the hammer?

Paul Nelson
Cell 708-670-6978
Office 512-392-2577
nelsonp@xxxxxxxxxxxxx

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John Brandt
Sent: Thursday, August 09, 2007 9:46 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: SQL views

OMG. The sound of reason.

Thanks Paul,
John Brandt
iStudio400.com
903-523-0708
MSSQL access FROM RPG

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Paul Nelson
Sent: Thursday, August 09, 2007 9:38 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: SQL views

I'll give you some of that, but with SEQUEL, I don't need to write much, if
any, RPG to do stuff, and I certainly don't need ODBC.

I see all the posters on this list struggling with SQL to manipulate data
(Updates, etc.) and I shake my head, knowing that using SEQUEL "I can name
that tune in 3 notes". :-))

Paul Nelson
Cell 708-670-6978
Office 512-392-2577
nelsonp@xxxxxxxxxxxxx

-----Original Message-----
From: midrange-l-bounces+nelsonp=speakeasy.net@xxxxxxxxxxxx
[mailto:midrange-l-bounces+nelsonp=speakeasy.net@xxxxxxxxxxxx] On Behalf Of
Nathan Andelin
Sent: Thursday, August 09, 2007 9:20 AM
To: Midrange Systems Technical Discussion
Subject: Re: SQL views

Paul N. wrote:
I'm reaching the conclusion that SEQUEL is a much better way to go.

I don't see VIEWS and SEQUEL as being mutually exclusive. SEQUEL queries
and reports can reference VIEWS, while VIEWS have the added benefit of being
also used within RPG programs, ODBC and JDBC interfaces, SQL CLI interfaces,
etc.

Nathan.