|
That's about what I thought, just taking a chance someone had some good news. Thanks, Bob > -----Original Message----- > From: owner-mapics-l@midrange.com [mailto:owner-mapics-l@midrange.com]On > Behalf Of David Leland > Sent: Monday, July 19, 1999 5:41 PM > To: MAPICS-L@midrange.com > Subject: RE: Modifications & Maintenance > > > In case you haven't yet discovered it, modifications are a real catch-22. > They seem to be so innocent and painless when you make them, but at that > point you've crossed over the line and have now made the upgrade process a > lot more work. My real advice would be to take out all the mods > you've made > and go vanilla code. If you absolutely can't do that, then make your mods > as invisible to MAPICS as possible. By that I mean, try not to > make direct > modifications to program code - instead use other techniques like database > triggers. > > I fight all proposed modifications tooth and nail and make 'em show me a > real business benefit for it and then I try to make them in a way > that will > disturb the least amount of MAPICS code. Lastly, I document all mods with > the thought in mind of future upgrades. > > I've been down the mods route and it is not pretty. > > Dave > > > -----Original Message----- > > From: owner-mapics-l@midrange.com [mailto:owner-mapics-l@midrange.com]On > > Behalf Of Bob Randall > > Sent: Monday, July 19, 1999 9:43 AM > > To: MAPICS-L@midrange.com > > Subject: Modifications & Maintenance > > > > > > What a topic. Does anyone have any advice on how to stay up with > > maintenance > > and continue with modifications? I have several mods to MRP, but > > now need to > > update maintenance on COM. Of course I can't do COM without > CAS, and can't > > do CAS without MRP, gotcha. > > > > I am considering applying maintenance to a separate environment and > > comparing programs afterwards. Cumbersome, but maybe my only > option. Other > > directions or thoughts are welcome. > > > > Bob Randall > > Airxcel, Inc. > > > > > > +--- > > | This is the MAPICS Mailing List! > > | To submit a new message, send your mail to MAPICS-L@midrange.com. > > | To subscribe to this list send email to MAPICS-L-SUB@midrange.com. > > | To unsubscribe from this list send email to > MAPICS-L-UNSUB@midrange.com. > > | Questions should be directed to the list owner/operator: > > dshaw1@infoave.com > > +--- > > > > +--- > | This is the MAPICS Mailing List! > | To submit a new message, send your mail to MAPICS-L@midrange.com. > | To subscribe to this list send email to MAPICS-L-SUB@midrange.com. > | To unsubscribe from this list send email to MAPICS-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: > dshaw1@infoave.com > +--- > +--- | This is the MAPICS Mailing List! | To submit a new message, send your mail to MAPICS-L@midrange.com. | To subscribe to this list send email to MAPICS-L-SUB@midrange.com. | To unsubscribe from this list send email to MAPICS-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: dshaw1@infoave.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.