Version control

[Nancy Palmquist]

Ken,

I make a subdirectory in the filepro file called: history

It will often be used for maps, edits, prc.,  out., screen., etc. 
Especially if I am making significant changes.

I manually copy prc. tables and append a date to the name, on some systems.
On some I just copy the process/output -whatever - to the history before 
I change it.  Then I always have the prior version of the table to 
recall if things go wrong.  This is not very granular and can be 
problematic if the start point is not workable anymore.

I also have one system that is much more extensive for updates.  I have 
the development, then I have a separate set of folders where I copy just 
changes to these folders.  On UNIX this can be done with scripts, on 
Windows I do it manually.

Then I can build an update from these folders and just send what has 
been changed.


I would hate to have every table saved before editing, it would be 
better to offer an option for a version start of some kind when you want 
it.


I am sure other people have more extensive methods than I do.  Since 
they are all manual, it tends to be something that can easily be 
overlooked, when you need it the most.

I try never to work on a Live system, that works best for on-going 
maintenance.

Not sure that will help, but it has worked for me for 20 years.  We have 
to work with the tools we are given.

Nancy

On 9/19/2014 5:36 PM, Ken wrote:
> Dear colleagues
>
> We have all dealt with version control problems in filepro.
>
> I would like to ask how some of you have dealt with it and what best practices you have encountered.
>
> Thamks
>
> Ken
> ‎
>
> Sent from my BlackBerry 10 smartphone on the Bell network.
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list

-- 
Nancy Palmquist
Owner
Virtual Software Systems - www.vss3.com
(412) 835-9417