× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: Client-Access and Excel
  • From: Buck Calabro <mcalabro@xxxxxxxxxxxx>
  • Date: Tue, 31 Aug 1999 13:57:18 -0400

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
Aptis; Albany, NY
mailto:Buck.Calabro@aptissoftware.com

> -----Original Message-----
> From: Chris.Chambers@v2music.com 
> Sent: Tuesday, August 31, 1999 11:31 AM
> To:   midrange-l@midrange.com
> Subject:      Client-Access and Excel
> 
> 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.
> 
> Is there a way to have the column headers carry the COLHDG names which
> would be
> more explanatory.
+---
| 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
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.