RE: w/%editc() - Qualified Names

>John,
>What's the difference between specifying a field named  XXNAME in SQL
>and using a co-relational name xx.name?
>I think if they want to query the customer master file, they would
>perfer to specify CITY, STATE, ZIP rather than CSTCTY, CSTSTE, CSTZIP.
>Besides, do end-users do JOIN functions when they run Query/400? If
>they're that smart, they can handle read field name.
>Bob Cozzi


I noted that Bob.

>....still leaves End Users
>who use (say) Query/400 to have to qualify names,  and forces the use
>of correlated names in SQL.
>While you can do that in both places,  It's a tedious effort that is
>not required if the DB is named that way.

It was from the other point mostly that I like the qualified name.
* to me *  it signify better where this "Instance" of Customer comes from.

It just seems more self-evident to me.

For you, Just Imagine there is a period in the center of XXXCUST.

XXX.Cust is transitory.  XXXCUST is Global.

Just personal preferences.

John