>Hello William!
>
>>in Las Vegas, one is in Arizona. We check out source, work, check it in, all >across a WAN with no problems. Don't worry about VCX files, I have checked >out and back in a number of class libraries without any problems.
>
>How do you able to work via WAN using VSS? AFAIK, it could work via RAS but I bet that it is a little bit expensive... Do you use any add-on for VSS for this matter?
>
>TIA

No add ons, straight out of the box as far as I know. The server holding the VSS is Novell 4.x (mixed environment with this company half Novell half NT a little UNIX), my workstation is NT 4, not sure what the other developers are using for a workstation platform but my guess is 9x. Before I connect to VSS, I authenticate to the proper Tree and Server (NOT the same as mapping a drive, I don't map a drive to the Novell box). Then I put in the UNC, \\DevServer\Source and VSS does the rest. Although I've never done it, I'm sure RAS would work just fine for this and would be fairly cheap unless it's a long distance call. To offset the cost, you could use VPN software on the server side and *probably* make a secure TCP/IP connection via the internet. VPN software isn't cheap though, but at least it would only be a one time charge. That's if the server were connected to the Internet.