|
It sounds like Joe has experience with a few generators. If all he had to base it on was AS/SET then I would have to hurl. But part of the problem is the tendency to want to look at the code. I think CASE tool users would be better off if source were generated into QTEMP and only the object kept. To remove the temptation. The problems I had with AS/SET were many fold: Their DB integrity was all code based and had nothing to do with RI or triggers. Generated RPGIII. Looking at that code was a mess. Failed to take advantage of new constructs, op codes, bif's etc. Generated code for ancient releases. When you stick with the code you don't have that problem. I often wonder how many shops install the latest and greatest versions of their ERP, yet run ancient versions of OS. I truly believe that many shops are begging their software vendors to say, 'Nope, this requires V5R1.' As a business case to management as to why they need to upgrade. I liked AS/SET for generating screens. And I used it for batch programs, only if they had a report. I never used their report programs. I also never modified code outside of AS/SET. I've been known to rewrite from scratch. Rob Berendt ================== A smart person learns from their mistakes, but a wise person learns from OTHER peoples mistakes.
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.