|
Why would these programmers use Access to analyze data on the iSeries? What's the matter with Query/400 or DBU or one of the many other tools? Paul Nelson Arbor Solutions, Inc. 708-670-6978 Cell pnelson@xxxxxxxxxx "Chaudhary, Sachin (GE Equipment Services, Consultant)" <sachin.chaudhary@xxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 01/21/2005 11:20 AM Please respond to Midrange Systems Technical Discussion To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> cc: Subject: RE: Link AS400 database wirh Access Database Yes you are right. There is already set of logical files and the processing/reports etc go perfectly fine in production env. I just wanted to do this for the new programmers who keep analysing data by opening files and running SQLs time and again. We do not have a separate test box:) -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Gary Monnier Sent: Friday, January 21, 2005 10:50 AM To: Midrange Systems Technical Discussion Subject: RE: Link AS400 database wirh Access Database There are many ways to solve your dilemma. One is, unless you really have your heart set on doing this through Access, is to use a logical file keyed in the sequence you want your query in and run your query over the logical view. Using this logical view will reduce the amount of time and CPU your query uses. And yes, it will take some CPU to build the logical view, but you can schedule it to be created/installed during slow hours. If your file is really enormous you may be better off writing a program to spin through it, filter out records you don't want to report on, write those that you do want to report on to a separate physical file and run your query over your new file. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx 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@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
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.