Bill,

I believe you are right that it is a Novell issue. Try going from low level mapping. What I mean by this is, do not use drive letters to map to your databases. I had this problem before and this is how I fixed it.

Good luck and HTH!



>Bill,
>
>There's a loud bell going off in my head.. I know I've had this problem before, but it was bout 3 years ago. Is M mapped via a server script or is it defined locally? I don't think this is a Novell issue, I think it's NT Workstation.
>
>If that doesn't work, double check the administrator profil on VSS and make sure the default drives are configured properly.
>
>HTH. I'll keep wracking my brain to see if I can specifically remember what did this. I don't think it's a bug
>
>>I am attempting to implement Visual SourceSafe (6.0 with SP4) with a VFP project on a Novell Network. If I set up a new database on my local C drive, everything workds fine.
>>
>>However, if the problem arises when I try to create a new database on a network drive. I try to create the database on M:\DEV, but something keeps changing it to the Novell path (\\GCC_CORP\VOL1\DEV\). SourceSafe does not seem to like this. It keeps saying it can't find the database, even when I point it to to the appropriate ini file.
>>
>>Has anybody here had this problem, and if so, how did you get around it? If not, does anybody have an idea where I might go to ask about this? I've checked at both Microsoft and Novell and haven't seen any bug reports of this nature.
>>
>>Thanks in advance,
>>Bill