|
Buck Calabro wrote: > > On Monday, June 22, 1998 12:22 PM, Rob Berendt [SMTP:rob@dekko.com] wrote: > > Field names on 400 versus those of Oracle. > > CREATE TABLE QTEMP/FILEY (BIGHONKINNAME FOR COLUMN LITTLENAME CHAR > > (10) NOT NULL WITH DEFAULT, EVENBIGGERHONKER FOR COLUMN SMALLNAME > > CHAR (25) NOT NULL WITH DEFAULT) > > Rob, > You're right on the money, but we're encountering a funny situation with > our Delphi developers. They're building tables on the 400 which get > system field names like BIGHON0001 and EVENBI0001 because they don't > bother with "for column" This causes our native AS/400 RPG apps and > end-user query tools to see the "funny" names instead of the longer, > useful ones. So, the moral of the story is that you have to provide the > long name for SQL *and* the short name for RPG/Query. Double work, sort > of. > > Buck Calabro > Commsoft, Albany, NY > mailto:mcalabro@commsoft.net > Exactly - or just fall back to 6 char uppercase RPG II names across the board and everything works :-) John Hall Home Sales Company. +--- | 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 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.