[RBG7-L] - Re: Developer Updates

[Emmitt Dove]

For operational differences, geographic identities, etc, I'd use a table-driven approach.  For instance, we have a payroll module that was set up to account for contractual differences at six different plants.  All the contractual information was stored in a table.  Also, each of our locations has a table where we ID the location itself.  And, after having to go through all our code and change the company name on reports, etc., once, we moved that into a table.  Now, if we change our company name again, I change one row in one table at each location instead of hundreds of reports and command files.

I have a question for the developers out there.  First, a little history.
 
I am developing an application for our schools nationwide.  Although the base application is the same for all the schools, some of the schools require customization due to geographic locations or operational issues. 
 
Therefore, what is the best way to manage these changes?  It would be quite a task to maintain a separate application for each school.  What about general updates to everyone's application?  What is the best way to approach these updates?
 
Thanks in advance for any feedback
 
Joel Solomon
Controller
Barbizon International
[EMAIL PROTECTED]

Emmitt Dove
Manager, DairyPak Business Systems
Blue Ridge Paper Products, Inc.
40 Lindeman Drive
Trumbull, CT  06611
(203) 673-2231
[EMAIL PROTECTED]
[EMAIL PROTECTED]