Hi!

From my 2-year experiense of using VSS for VFP projects I never had any serious problems or limitations with it. Specially such things as limitation of method addimg. It never was a problem. In addition, I'm project lead in my team too, so you can point him to this thread, if you want and if you're sure he will not hate you after this ;)


>Thanks for your answer. I need a detail that's a bit more specific: I know that SourceSafe can do all kinds of wonderful things, but why would the other developer love everything about VSS, except he tells me that, from personal experience, it doesn't do well on method code? Like you say, that text representation file seems to work quite well, IMO. Do you have any insight on this? Since he's the project lead, I've got to follow his lead, and I'm not sure I can go back to .PRGs for everything, and not write a custom method ever again...
>
>As far as check-in remarks -- great idea. But programmers well-disciplined enough to write them? Yeah, right! <vbg>!
>
> - della
>
>> Of course you can! and you can track all changes!
>> Think: for what VFP makes third file for each form, report, class lirary in text format and store it in VSS and check out/check in it together with other fiels? This file (with extension scc, fcc, vcc, as I remember) contains full text representation of your form that can be used to track changes by comparing this file with older version.
>> In addition, in our team we use check in remarks, than report all check ins and have complete list of what were changed by all programmers during certain period with remarks ready to prepare list of changes in next version of application (of course, if programmers well-disciplined to write all these remarks ;)
>>
>>
>>>I've just joined a new project team who uses SourceSafe. The other project teams I've worked on did not use any kind of source code control, so I've got no experience to draw on, except the experience of you wise people (or wise acres, in some cases <g>).
>>>
>>>The situation that I've been told not to add methods to a form (for example, don't create a method Ask2KeepChanges that is VERY specific to the form), instead I should use a separate PRG because VSS cannot track code changes very well. The example cited to me is that if you change the font of one button on a form, VSS sometimes becomes worthless at tracking other changes, especially code in methods.
>>>
>>>Does anyone have any experience as to why someone would come to this conclusion? Please tell me that I can still add my own methods and VSS will be happy!!
>>>
>>>THANKS!
>>>
>>> - della Martin

Vlad Grynchyshyn, Project Manager, MCP
vgryn@yahoo.com
ICQ #10709245
The professional level of programmer could be determined by level of stupidity of his/her bugs

It is not appropriate to say that question is "foolish". There could be only foolish answers. Everybody passed period of time when knows nothing about something.