Did anyone bother testing SQL???

In "Define a new SQL Statement" I put:

select

a.*,c.*

from

DISTV3.BASE_ST as a

left join DISTV3.REL_ST_STF_1M b
        on a.stkey=b.stkey

left join DISTV3.BASE_STF c
        on b.stfkey=c.stfkey


This FAILS when I hit "Parse" but obviously shouldn't, and it works fine
in iSQL.

So I think to myself, why not just use the visual tool to build the
query and see what it comes up with. First, the list of tables is NOT
sorted in any way. Hello, I have a lot of tables and NO WAY to sort
them. This is absolutely unacceptable in this day and age and with a
product intended to connect to a DATABASE machine.

So still thinking this might be a USABLE tool, I go into the visual
editor and build the same query as above. The first thing I notice is
that the join window is not resizable. The query I'm really trying to
build will ultimately have about 60 tables. How the hell am I supposed
to work with that in a fixed-size window (assuming I can find the tables
I want to use in the unsortable list)? All my joins are left joins and
there's no way to set the default...so I'll get to change that about 60
times. Joy.

But here's the great part. After going through all that crap, the SQL
generated isn't valid and doesn't parse! Here's what it generated:

SELECT 
   DISTV3.BASE_ST.STKEY, 
   DISTV3.BASE_ST.STTYP, 
   DISTV3.BASE_ST.STTTL, 
   DISTV3.BASE_ST.STSTL, 
   DISTV3.BASE_ST.STPST, 
   DISTV3.BASE_ST.STEML, 
   DISTV3.REL_ST_STF_1M.STKEY, 
   DISTV3.REL_ST_STF_1M.STFKEY, 
   DISTV3.BASE_STF.STFKEY, 
   DISTV3.BASE_STF.STFNAM, 
   DISTV3.BASE_STF.STFEML, 
   DISTV3.BASE_STF.STFMSGTYP, 
   DISTV3.BASE_STF.STFMSGID, 
   DISTV3.BASE_STF.STFSTS, 
   DISTV3.BASE_STF.STFPOS, 
   DISTV3.BASE_STF.STFPIC, 
   DISTV3.BASE_STF.STFBACKUIDFROM
   DISTV3.BASE_ST LEFT OUTER JOIN DISTV3.REL_ST_STF_1M
ON 
   DISTV3.BASE_ST.STKEY = DISTV3.REL_ST_STF_1M.STKEY ,
DISTV3.REL_ST_STF_1M LEFT OUTER JOIN DISTV3.BASE_STF
ON 
   DISTV3.REL_ST_STF_1M.STFKEY = DISTV3.BASE_STF.STFKEY 


Notice that REL_ST_STF_1M appears twice, the formatting makes no sense,
and where on earth did those extra commas come from? Nobody tested a
multi-table join? Baffling!

I'm forced to ask, how the hell am I supposed to get my query into this
"tool?"

Yes, I've updated everything to the latest code.
 
NOTICE: This E-mail may contain confidential information. If you are not
the addressee or the intended recipient please do not read this E-mail
and please immediately delete this e-mail message and any attachments
from your workstation or network mail system. If you are the addressee
or the intended recipient and you save or print a copy of this E-mail,
please place it in an appropriate file, depending on whether
confidential information is contained in the message.