|
> From: rob@xxxxxxxxx > > Last I knew it was a real pain to Query/400 a stored procedure. We're > talking about users that upload data to the i5 from their PC's because > they like Query/400 as a reporting tool. Let's see here: some users download data to the PC to run reports, and some users upload data to the iSeries to run reports. Basically your users do whatever they want whenever they want with whatever tool they like. I could see how in that environment any sort of standards would be difficult to implement, and without standards it's really hard to implement good IT practices. I can't imagine how you get through sarbox, though. > And yes, if you change the underlying database then you have to change the > queries, etc. But that only happens about every 6 years so it's something > we'll deal with on an "as occurs" basis. HAHAHAHAHAHAHAH! Only every six years. Oh my, if my clients could make it through six years without database changes, I'd be ecstatic. I just thought of something: we made database changes just for the little project I did for Dekko! I don't know how that jives with your "once every six years" statement. Joe
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.