Version control

[Richard Kreiss]

Ken,

At the top of my processing tables, I have the creation date, version # and then a summary list by date of the changes made to the processing table.

I also save a copy of the table prior to making changes. This is the process name_version number.  I will normally keep no more than 5 versions back.

Since I maintain copies of all of my client's programs on my system, I will move older versions to my system.

I have been working on writing a program to analyze the processing tables. I am doing this using filePro.

What I am attempting to do is post to separate files the program, indexes, dummy fields and long variables which are used in the processing table. Each of the files as the filePro file, the process table name, as well as a list of other programs which might be using the same item.

The program file has the file name, program version #, date and a description field so as to have a brief description of what the processing table is for.

In the case of dummy fields and long variables the record, which will have to be manually updated, shows what the variable or dummy field is used for.

The real problem arises in that filePro does not allow for the selection of what processing table to use as the automatic process table during syntax check. The only way to accomplish this is at the command line which is an extra step which I have to assume most filePro program is do not do. I always have to remember to making changes to processing tables that use a different order processing table then auto, to get to the command line and type in rcabe filename -z name -y name -c so that the program is tokenized the correct order process table.

The other advantage to doing what I'm trying to do is that if it is necessary to make a change to a variable, one can easily find where that variable is being used. Since the filePro files can be indexed, one could check to see a given variables name and what processing tables and what files it is used in.

As for the indexes, having an explanation of why the index is in existence and what programs are accessing it can make it easy to locate the program or programs which might be causing problems with the index.

The main problem I'm running into, as you probably have surmised, is hashing the processing table to break out this information automatically and post to the proper file. I have one fairly complicated file which creates HTML and parses HTML and does a lot of posting to whether filePro files. This is been my test processing table and it is proving more difficult than I originally thought.

I have a feeling there are better tools for doing this in *NIX but I live in a Windows world and would like to continue this exercise using filePro.


Richard Kreiss
GCC Consulting

Office: 410-653-2813




> -----Original Message-----
> From: Filepro-list [mailto:filepro-list-
> bounces+rkreiss=verizon.net at lists.celestial.com] On Behalf Of Ken
> Sent: Friday, September 19, 2014 5:31 PM
> To: FilePro Mailing List
> Subject: Version control
> 
> An HTML attachment was scrubbed...
> URL: <http://mailman.celestial.com/pipermail/filepro-
> list/attachments/20140919/91b7531c/attachment.html>
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list