I've also had this problem before. It was caused by trying to rebuild a project when someone was running it.


>>I encountered this problem and it turned out to be
>a path problem for the cursor, check the path of the
>cursor in the data environment, and make sure that
>any coding has the exact path for data environment
>so there isn't any question about where it's going.
>
>
>
>Mark,
>>
>>I've used VSS over a modem and it certainly does call for some improvisation. Still, this approach defeats one of the major features of source control software which is to make it difficult for people to modify code they don't have checked out.
>>
>>>>Hmmm... This makes me really nervous. It will only be a matter of time before you forget that you're not working with a checked-out copy. The next thing you know you'll make a bunch of changes then blow them away when you check out or update the files.
>>>
>>>been doing it this way for almost a year now and haven't screwed up yet! (knock on wood)
>>>
>>>my approach is framed by the large project size (248 files) and the fact that I use VSS over a 33.3 modem connection. I can't imagine having to check all the files out everytime I want to build an app to test my changes!