|
-- [ Picked text/plain from multipart/alternative ] Steven why are you stuck with Query? Steven Donnellan wrote: >If only I could program in RPG <sigh> >I'm stuck with QUERY/400... > >Steven Donnellan >AS/400 Systems Manager >IBM Certified Specialist - AS/400 Professional Operator >Simon Jersey Ltd > >http://www.simonjersey.com > > > > >jpcarr@tredegar.com >Sent by: midrange-l-admin@MIDRANGE.COM >07/10/01 00:54 >Please respond to midrange-l > > > To: midrange-l@midrange.com > cc: > Subject: Re: QNTC > > > > > > > CPYF FROM(MYLIB/MYDBF) TO (QNTC/MYNTSERVER/MYDBF.TXT) FIELDS >(*FIXEDLENGTH) > >The idea is to put some databases on an NT server so that MS Access can > >play about with them, without the long long wait associated with ODBC. >The > >databases are created over night, so real time access isn't an issue. > >Steven Donnellan > > >Personal opinion, If you just want to write a Fixed Length .TXT file to >directory >QNTC/MYNTSERVER I would do it from RPGIV. Very Easy. That way you >would >have control and do other things like Reading One file, Chaining to >another >format the output fields in what ever order you wanted easily. > >The one thing I see wrong with CPY (and all variations) is that you have >to >do gymnastics to get the Source file right to do the copy. With RPG, I >can >leave all the info in my Normalized files and just read/chain, etc to >format the >output record and write directly to a PC file format. No intermediate >work >file >to get it there. > >I have many Production programs that do this exact thing. Mostly to a >.CSV >file >which people then access via Excel. I even have an exit routine in >certain >Add/Change/Delete file maintenance programs to write the file to the IFS >upon exit > if any record was changed. This way my DB2 file is always in sync with >my >PC file on the IFS. > > >I will be showing this Technique at COMMON in one of my sessions. > >John Carr > > > > >_______________________________________________ >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. Regards, Glenn Ph. (718)898-9805 <mailto:Glenn-Ericson@att.net>mailto:Glenn-Ericson@att.net =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= --
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.