The non-specific SCC error is spurious and can be ignored. However you may not be able to get rid of it short of starting a new p[roject file.

>>I just went through this a couple of weeks ago. I was only willing to put a certain amount of time into it, so will not say it won't work, but I could not get the piece I was after to work. What I wanted to do was have VFP generate SCA and VCA files at check-in time, as it did with VSS. I was able to download and install a provider called MSSCCI. The problem I ran into was I am working with an existing project which was already in TFS. When I made MSSCCI the active source control provider in VFP's Tools/Projects dialog, it kept wanting to add the VFP project to TFS. Maybe that would have worked but I didn't want to take a chance on royally screwing things up. I am still fairly new here and several of us work on this project. That wasn't the kind of entrance I had in mind ;-)
>>
>>FWIW I got an email from LearnVisualStudio.Net recently saying they have some new videos on TFS. From what I know about TFS at this point (not that much), I don't think much of it is going to be applicable to VFP. I think we basically got left in the lurch when Microsoft replaced VSS with TFS.
>>
>>Good luck!
>
>
>Mike,
>
>With regards to your specific problem, we did find that we had to go through the Join Source Control Project menu option to set the current folder within TFS before attempting to add the VFP project. That might resolve your situation.
>
>However, we're running into a weird problem. When trying to add our project, we get the "non-specific" SCC API error on a bunch of our image files that are part of the project and we have no idea why. The files exist, and when I create a brand new project that has one of the failed bitmaps, it gets added fine to TFS.
>
>So, we're basically stumped and stuck.
>
>Jon