RE: dds, sql , ODBC alias...

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--
[ Picked text/plain from multipart/alternative ]
Thank you, I just tried this...  Do you know if these fields are recognized,
by RPG programs, if I don't refer to them by name?

Meaning, if I have 3 PF's (tables)  and I uses the same Alias in all 3
files, ie: (customer_number)  will these 3 fields be qualified in RPG?  If I
use the prefix command?  Or does RPG recognize alias's at all?

I trying to avoid accidentaly overwriting data...

Thanks,  tim

> -----Original Message-----
> From: rob@dekko.com [SMTP:rob@dekko.com]
> Sent: Tuesday, October 30, 2001 6:15 AM
> To:   midrange-l@midrange.com
> Subject:      Re: dds, sql , ODBC alias...
>
>
> Tim,
>
> Try this.
> I had this DDS:
> R TIMR
>   ACOL1          6A
>   ACOL2          6A
>   ACOL3          6A
>
>                       Record  Format Level
> Format       Fields   Length  Identifier
> TIMR              3       18  2B2D75F4432DB
>
> I changed it to this DDS:
> R TIMR
>   ACOL1          6A         ALIAS(BIGHONKINGFLD1)
>   ACOL2          6A         ALIAS(BIGHONKINGFLD2)
>   ACOL3          6A         ALIAS(BIGHONKINGFLD3)
> Then ran CHGPF FILE(ROB/TIM) SRCFILE(ROB/QDDSSRC)
>                       Record  Format Level
> Format       Fields   Length  Identifier
> TIMR              3       18  2B2D75F4432DB
> Kept my data, and my record format level id.
> Then I ran STRSQL and
> select bighonkingfld1 from tim
> and
> select acol1 from tim
> and got the same results.
>
> I thought of this years ago when an old coworker (from the PC arena)
> called
> me up years ago.  Seems that the company he worked for had designed a PC
> based system with big field names and the 400 people used gross 6
> character
> field names.  400 people were trying to pull muscle to get the PC people
> to
> change all of their field names.
>
> Rob Berendt
>
> ==================
> "They that can give up essential liberty to obtain a little temporary
> safety deserve neither liberty nor safety."
> Benjamin Franklin
>
>
>
>                     "Hatzenbeler, Tim"
>                     <thatzenbeler@clini       To:
> "'midrange-l@midrange.com'" <midrange-l@midrange.com>
>                     tech.net>                 cc:
>                     Sent by:                  Fax to:
>                     midrange-l-admin@mi       Subject:     dds, sql , ODBC
> alias...
>                     drange.com
>
>
>                     10/29/2001 05:06 PM
>                     Please respond to
>                     midrange-l
>
>
>
>
>
>
> This message is in MIME format. Since your mail reader does not understand
> this format, some or all of this message may not be legible.
> --
> [ Picked text/plain from multipart/alternative ]
> This is a weird question....
>
> I have an as/400 application that uses a DDS described databases...
>
> The rpg programs all use the fieldnames defined in the files...  But, is
> there anyway to setup an alias, so when the uses use Crystal Reports, via
> the ODBC, that they can see different fields names (longer more
> descriptive)
>
> I want my current programs to use the ugly short names, and the ODBC
> requests to see the pretty names...
>
> Thanks, tim...
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
>
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.