LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous messageNext messagePrevious in topicNext in topicPrevious by same authorNext by same authorPrevious page (April 1997, week 4)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:   Mon, 28 Apr 1997 11:27:00 EST
Reply-To:   "Kagan, Jerry" <KAGANJ01@IMSINT.COM>
Sender:   "SAS(r) Discussion" <SAS-L@UGA.CC.UGA.EDU>
From:   "Kagan, Jerry" <KAGANJ01@IMSINT.COM>
Subject:   How do you manage customized AF applications?


I've run into a serious AF application management problem. I have an application that I've been asked to repeatedly customize for various customers. Now I have multiple versions of the same basic application, all with minor differences. This is becoming a maintenance nightmare. When I make a change in one application, I have to repeat the change, and repeat the testing of the change, in every customers version.

I have a tools catalog containing all the truly generic code that can be accessed by any application. That helps. I was hoping to use the new CATNAME option for the AF command (v 6.12) to concatenate the main (or standard) application catalog with catalogs containing only the modified entries for each customer. That would have been the ideal solution, but the CATNAME option doesn't work (SAS should be issuing a usage note about this soon).

I find it hard to believe that nobody else is running into this problem. But, I see no SUGI papers about it, and no threads on SAS-L, and SAS says that I was the first person to discover the CATNAME bug. So, how are you all managing customized versions of AF applications?

Thanks for any help!

-- Jerry Kagan - Yet another SAS Consultant

Back to: Top of message | Previous page | Main SAS-L page