>>Ah, there it is. Still no joy, though. When I try to join the TFS project it keeps wanting the local project to be one level below its actual location. i.e. server path is $/xxxx/yyyy (correct) and it wants the PJX to be in c:\xxxx\yyyy\yyyy (incorrect).
>>
>>I am going to put this aside again, at least for now. It may well be a Mike problem rather than a TFS or VFP problem.
>
>Mike,
>
>Not sure what the issue is there.
>
>My new problem is that the adding the project seems to be working but the interaction between VFP and the TFS provider is frustrating. When going through all of the files in the project to add to TFS, I'm being prompted by the TFS provider on each file to check it in. Considering how many files we have in this project, this initial adding of the project has become a herculean task.
>
>I recall the days of using PVCS and having the project add to source control loop through all of the files and check them in without any user interaction until the whole thing was done. While I understand this is a one time initial setup, it's one of the most painful I've ever seen.
>
>Jon

I did figure out what was wrong earlier. There is a dialog in TFS associating server folders with local folders, and it had been set up incorrectly by a previous user of this machine. I fixed that and blew away the local folder structure. It is currently refreshing via Get Latest Version.

Now we'll see if I can get the integration the rest of the way I want to go....