Hi Paul

Excellent reasoning! Then the solution might be to use a project hook and to call the scctext without the time-wasting process of indicating which files are checked in and out in the project manager.

>>Well, now it's your turn to enlighten me. Under what circumstances do you need to use DIFF functions to see the changes? I assume it's so you can see the revisions made over time?
>
>It's not something I use everyday, but when I need it, I'm >really< glad it's there. For example, you've made some changes to some class library to fix some other problem. You test everything and send it out. A few weeks later people start complaining about some weird problem that you've never had before. You don't can't think of anything that you would have changed that would cause this problem. A diff at this point can sometimes point the problem out in a few minutes, as opposed to spending a bunch of time searching through your changes manually and seeing if any of them could cause a problem (in some cases, you don't even see the error until you can compare the original code to the new code).
>
>Another place where it's handy is when a developer makes a "small" change and doesn't think they need to comment it. It, of course, causes some problems. Now we want to find out who/when/why the change was made. A diff. will tell us at least who/when.