Thank you Tek-Tips for this forum

[JDurbin]

Now let's start out this forum by providing a Siskel's comments to Robert's (Ebert) comments in the other thread before this forum opened.

* the default behavior is to checkout a file if you open it from the Project Manager;
This might be the default but doesn't have to be

this means that when people go to simply look at code from within the PM, they automatically check the file out; often, the user is unaware of this,
hmm hopefully not getting paid too much if they are that unable to pay attention to details

and they go and make "test changes" to the file, then inadvertently check it back in, even though it wasn't their intention.
my comments above * 100

allowing multiple checkouts is risky.
even if it's considered risky you don't have to allow it. In fact the 'default' here is not multiple checkouts. Even from a single checkout point of view many find VSS's ability to rollback to previous versions enough of a reason to use VSS.

From a technical standpoint, it exponentially increases the chances of corruption, as VSS must assemble and resolve changes made by multiple poeple at the same time.
This is not entirely correct. The user is presented with a merge screen and has many options. It's not like you're at the mercy of a robotic VSS.

From a management standpoint, you don't want developer "A" making changes to a class or form independant of developer "B" when the changes by both could impact the other.
So pieces of the project are distributed everywhere? There has to be a plan, organization and common sense in a team environment when working on the same project either way.

A little awkward with the usual unusual M$ 'features' but I give this picture a "thumbs up"
[sig]<p>John Durbin<br><a href=mailto: john@johndurbin.com> john@johndurbin.com</a><br><a href=

http://www.johndurbin.com>

</a><br>MCP Visual FoxPro<br>
ICQ VFP ActiveList #73897253[/sig]

 

[TomasDill]

Hi!

* the default behavior is to checkout a file if you open it from the Project Manager;
This might be the default but doesn't have to be
I remember, there are options somewhere in VFP that allow to specify default behaviours for automatic actions. I'm sure, you can switch off automatic files adding to VSS. Probably, you can switch off automatic check out as well. Anyway, this behaviour is in developer application that uses VSS (here - VFP 6).

this means that when people go to simply look at code from within the PM, they automatically check the file out; often, the user is unaware of this,
From my experiense I never had a situation when someone else than developers look to code in project. When we send sources to customer, we take all files from VSS, detach project from VSS, remove read-only attribute, clean up all sca/fra/vss/... files created in VFP for VSS (we have special script for that) and than send. Allowing customer to look into project under VSS with risk of doing something (for example, checking out files), is quite bad thing, IMHO. Never do this. Just good organization, nothing more.

allowing multiple checkouts is risky.
We always restrict multiple checkouts in VSS. So, when file is checked out, VFP will not allow to check out it again, VSS too. Other applications too. VSS have such option.

From a technical standpoint, it exponentially increases the chances of corruption, as VSS must assemble and resolve changes made by multiple poeple at the same time.
It looks like you do not know the purpose of VSS at all. VSS is designed to do not allow to make changes to module by multiple people at the same time. It was a job of VSS from its birthday. Of course, when you allow multiple checkouts in VSS, you might have problems. John is right, you have options and its up to you how you use them.
As about corruption, you can rollback file changes to any point you want in VSS. If file corrupted, you just rollback changes 1 step back. Much like backup. Nothing new here. And it is on the level of each file, so it takes little time to do that compare to extracting files from nightly backup.

Hope, this will clean up things for all guys that think MS VSS is only headache and using of third-party source safe control applications will give MUCH of advabtages, that is not correct, of course.

[sig]<p>Vlad Grynchyshyn<br><a href=mailto:vgryn@softserve.lviv.ua>vgryn@softserve.lviv.ua</a><br>[/sig]

 

[JDurbin]

BTW, and I think I speak for Vlad here too hopefully, we are 'jumping' on Robert's statements since it should be obvious he is an accomplished programmer and recognized as such here and thus should be able to take the 'heat' w/o it appearing we are trashing him. We love ya Robert just gotta spice up this forum. heh [sig]<p>John Durbin<br><a href=mailto: john@johndurbin.com> john@johndurbin.com</a><br><a href=

http://www.johndurbin.com>

</a><br>MCP Visual FoxPro<br>
ICQ VFP ActiveList #73897253[/sig]

 

[TomasDill]

Sorry, if my words were too hard. Anyway, I didn't mentioned someone's name... [sig]<p>Vlad Grynchyshyn<br><a href=mailto:vgryn@softserve.lviv.ua>vgryn@softserve.lviv.ua</a><br>[/sig]

 

[JDurbin]

LOL. I'm just exercising the proverbial CYA in this politically correct, over sensitive world. You never know <s> [sig]<p>John Durbin<br><a href=mailto: john@johndurbin.com> john@johndurbin.com</a><br><a href=

http://www.johndurbin.com>

</a><br>MCP Visual FoxPro<br>
ICQ VFP ActiveList #73897253[/sig]