RE: STRSQL

I prefer ACS, and find that if I can't remember names (which is most of the time), I'll just do a "select * from...." and the column names are displayed with the first data to come up (instead of the DDS defined COLHDG text). Perhaps it's because my files are all DDS defined, not DDL... I don't know if that makes a difference. So even though defined column headings are normally preferable, the way this works out makes it handy.

Bill Reed


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John R. Smith, Jr.
Sent: Thursday, August 10, 2017 3:30 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: STRSQL

I find I still use STRSQL because I never remember the field names and I can't prompt in ACS.

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Vernon Hamberg
Sent: Thursday, August 10, 2017 3:25 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: STRSQL

In addition, STRSQL does not support a lot of the new stuff in SQL, anyhow.
For prompting, that is - things like WITH ___ AS are not promptable.

I cut my teeth on STRSQL starting 25 years ago (Yikes!). I still use it occasionally, there are options (F13) I'm more used to, but I'm finding them in ACS as well.

Cheers
Vern

On 8/10/2017 1:46 PM, Rob Berendt wrote:

I agree that Run SQL Scripts (from ACS)does not have the field
prompting which is nice. However, even for "quick and dirties" I will
rather use Run SQL Scripts. I've found that the prompting does just
get in the way for all but the most basic queries.
Using prompting is a crutch. Many people will not step out of their
comfort zone on queries which go past prompting.

The ability to "Insert from examples", and to write your own, in ACS
is very nice.


Rob Berendt