>
>I am wondering if I could create a project hook class that could update a shared project that is stored on the network. Then, when a user wants to update the project they can just copy down the shared project.
>
>However, when a user adds a file to their project, the hook class would open the shared project, add the file, then close the shared project. If a user removed a file, the same thing could happen.
>
>What do you think?
>
>BOb

Good idea. I think that would be very doable. I'm not sure if you could provide this seamlessly though (comparing PJX files for differences and automatically merging changes etc etc).

In any case, you could give people the following options:
1) Retrieve current copy of project from the shared area
2) Allow a developer to "check out" the project for updating
3) Allow a developer to "check in" the project after updating

You could manage the check out/in via source control program or just have it in a shared directory somewhere.

This probably wouldn't work for us, however, since we would like to continue using the integration features between VFP and VSS. I think this would work fine if you are running VFP and your source control program separately though.

-Doug-