managing a dev system

[Richard Kreiss]

> -----Original Message-----
> From: filepro-list-bounces+rkreiss=verizon.net at lists.celestial.com
> [mailto:filepro-list-bounces+rkreiss=verizon.net at lists.celestial.com] On
> Behalf Of Richard D. Williams
> Sent: Thursday, March 13, 2014 6:52 PM
> To: filepro-list at lists.celestial.com
> Subject: managing a dev system
> 
> Does anyone use a development system for testing ?
> 
> How do you make sure all changes are made after a new program is tested?
> 
> Lots of notes?
> 
> Richard

I maintain a development area on a client's system.  All of my processing tables have:

1. The file name
2. the processing table name
3. creation date
4. version #
5. modification date and brief explanation of the modification made

Prior to making any changes I save of a copy of the current table process table name_mmddyy.  This allow me go roll back to a previous version fairly easily if the is a problem of if I really mess up the current table.

I can compare version numbers and date of last change to see if the most current version of the program is running.

The header portion of my processing tables tend to grow as time goes by as I add  in the changes.  

I have often thought of building a database to maintain the changes but that would be more work.


Richard Kreiss
GCC Consulting

Office: 410-653-2813