RE: Client-Access and Excel

[John P Carr <jpcarr@xxxxxxxxxxxx>]

>This isn't an answer to your problem, but we find the exact opposite to be
>true.  Rather than use the DDS field names (artificially held to 6
>characters for RPG/400 compatibility), we use the ALIAS to have longer,
more
>user friendly names.  If there's a way to use the COLHDG values instead,
I'd
>love to hear how it's done!
>Buck Calabro

>>When importing a DDS defined file using the new (?) client access facility
the
>>column headers in the resulting spreadsheet carry the ALIAS names of the
fields
>>which are COBOL and thus not as user friendly as they could be.
>>Chris Chambers

It appears that CA/400 uses the ALIAS description for it's description,
However
I think that is just a coincidence.   It really uses the description from
the FOR
description as defined in SQL.   It just so happens that the SQL keyword
FOR description Maps to the description in the DDS ALIAS keyword.  
 For example.

Create Table mytable
        (fielda                         Dec(7,0) Not Null,
         fieldb For BIGNAME             Char(30) Not Null)


("For BIGNAME"  means the same as DDS ALIAS)

Using the FOR keyword in SQL will also give you the 
DDS  ALIAS keyword function.   

So if you want the fields to have text in CA/400, use the
DDS ALIAS keyword, or use the FOR SQL  function, 

John Carr


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---