× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Suggestions for maintaining source code
  • From: "Shrader, Patrick" <pshrader@xxxxxxxx>
  • Date: Fri, 18 May 2001 13:08:33 -0400

Like many of you, over the years we have had to modify some MAPICS source
code. I consider myself extremely lucky in that the modifications have been
whittled down to a half dozen programs, but I still have to manage these
changes as if they were a hundred changes.

Because of these few changes I don't stay current on my PTFs. Now I am
embarking on the process of upgrading several PTF levels over the next
couple weeks. However, I need to verify that the programs that I have
modified are not changed in the PTF. What are some ways that you insure that
your modified source code is at the correct version -- especially when you
install multiple PTFs?

I have thought to save the original MAPICS objects to another library and
compare the versions after the ACSAPPLY. If they don't match then I will
download the latest source and make the modifications. 

What are your suggestions?

Patrick



+---
| 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: 
|daveshaw@bellsouth.net
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.