All,

I'm looking for ideas on how to implement this myself or even discover an off-the-shelf solution.

I work from 1 of 3 PCs on any given day. These are physically different machines. Due to the nature of my development environment, I need all my work to reside in the same folder on all the machines so I have a work folder called C:\Work on all 3 PCs.

Monday I use PC_1 and make changes to the C:\Work folder on PC_1. Tuesday I need to use PC_2. I go to PC_1 and upload the entire C:\Work folder to a server share (5 minutes). Then I go back to PC_2 and download the Work folder from the server share to the local filesystem on PC_2 (5 more minutes).

I had considered all 3 PCs instead of using a local resource, to use a network drive like \\server\mySharedWork. That way, all 3 PCs would map say W:\ to \\server\mySharedWork. That way they would all have the same configuration and all 3 would always have access to the most recent development environment.

I had to reject the \\server\mySharedWork solution because I go on the road alot to deploy software to customers, and obviously the network resource is gone. If I were to make a local copy of \\server\mySharedWork then the W:\ is no longer consistent. The local Work folder would have to be somewhere besides W:\.

So, I need a way to have a local folder like C:\myWork that I can use and it should self-synchronize with a network share like \\server\mySharedWork when the shared resource is available, and ignore the shared resource when it is not available.

Sorry for the long-winded post, hope you were able to digest all that.

Any ideas? This can't be the 1st time someone wants to do this.

P.S. I have a local Windows Workgroup, not a Windows Domain.

Dave