home.png Alternate SCCText

Improved source code control to text program for use with Visual FoxPro's IDE.


Note: this project has moved to GitHub: https://github.com/VFPX/AlternateSCCText

This new and improved version of the source code control to text program was developed years ago by ProLib and released for all Visual FoxPro developers to have a better source code control experience. Jürgen Wondzinski, aka "wOOdy", is the project manager for this project.

There are several improvements made to the original SCCText.prg included in Visual FoxPro:
  • Consistent and case insensitive sorting of methods, objects, and properties
  • Corrects several bugs in the original version shipped from Microsoft
  • Optimizations
  • German, Spanish and French localizations
This routine has been in the Fox Community for many years now and is accepted as the "better standard" by Fox developers around the world.

vfpxreleasesmall.png Latest Release of Alternate SCCText

Last edited May 3 at 4:30 PM by DougHennig, version 14


mattslay Jun 10, 2011 at 3:43 PM 
I've posted code on StackOverflow showing a PRG that will automatically genereate SCC files for each file in the Active Project. http://stackoverflow.com/questions/6125103/how-do-i-manually-generate-text-files-for-entire-project-to-diff-in-visual-foxpro/6245269

kainhart Feb 24, 2010 at 7:54 PM 
In response to jstager, this is generally why when you make a general formatting change in any source control situation you want to do it for all files or a group of files at one time and do it independently of any behavioral changes. This way you only see a batch of formatting changes and then all subsequent diffs done to look at behavioral changes will have not have that formatting noise.

wOOdyProLib Dec 20, 2009 at 8:21 AM 
@Stefan: The "Laste edited" ist targeted to changes of this particular webpage, not changes to the codebase referenced from here.

StefanWuebbe Dec 20, 2009 at 7:35 AM 
Probably not exactly a show-stopper: the readme.txt included in the download ZIP mentions "Readme for SccTextX, Version 2008-11-12", as opposed to "Last edited Jun 24 at 8:27 AM by craigsboyd, version 13"


amariottini Sep 24, 2009 at 7:47 AM 
Yes, this is by design but maybe this could be enhanced.
By now I solved commenting out the read-only check and simply let SccTextX to overwrite any text file.
Another problem with VFP integration with source control systems is that after a rebuild of the project all forms, classes, etc.. become checked-out so I have to re-check-in all of them spending a lot of time and changing without need the version number (and growing repository). This is a very bad behavior, I know that build modify the vcx and/or vct files but the source code is not touched, so why other developers have to see them as modified? Is there any workaround for this?
There are very few informations in internet about VFP and source control systems integration so I'll appreciate any suggestions.

wOOdyProLib Sep 21, 2009 at 5:23 PM 
Hi Amariottini, this behaviour should also show up with the original Scctext, thus it's not a bug from that newer version.
But I see your point. Will play with that problem and try to implement some additional functionality.

amariottini Sep 15, 2009 at 2:50 PM 
When the project is rebuilt all classes and forms etc.. are modified and marked as checked-out but text files generated by SccTextX are still read-only so on check-in I have a lot of requests to overwrite these files.
How can be solved?
Maybe you could add a flag "overwrite all"?
Or there is workaround?

jstager Nov 14, 2008 at 1:53 PM 
Guys is there anything that can be done with the fact that once you start using this new version of SCCText and compare the differences to a history item, everything is different because of the order of things? Therefore trying to compare versions that were produced with the old & new SCCText is kind of useless.

Is this more of a going forward thing?