I'm having a heck of a time setting up VSS.

I installed the server edition and created a database. Then (based on something I read here) I didn't add files using the VSS Explorer - instead, I went back to the client, opening the Project Manager, and chose "Add Project to Source Control".

That seemed to be working - except that it failed to add some of the files in the project. The pattern seems to be that it added all of the files from D:\PROJECTS\MYPROJ (and they now have padlocks next to them in the VFP project) but it generated errors on all of the files in D:\PROJECTS\COMMON (and its subdirectories).

The error message was the same as when I now try to add those errant files manually (through Project > Source Control > Add Files to Source Control), namely:

"File d:\projects\common\programs\myprog.prg could not be mapped to the SourceSafe project $\newproj."

There's no difference in network rights on those two directories and I have no trouble accessing the ones in \COMMON from the client (i.e., they do exist).

So what am I doing wrong? The only related message I found on UT suggested to the writer that he always run VSS directly rather than through the VFP project manager. Is that really necessary?? That seems like an awful PITA.

I have a couple of other questions which I'd post separately except that it occurs to me that they might be related.

1) The server edition is running under Win98 and the client on WinNT. I understand that it would be better if the server were running under NT ... but I can't do that now for various reasons.
2) Under these circumstances, does the VSS server app need to be always running on that machine?

Thanks for any help.

-Bob