Really annoying "Can't edit module" error message

I have two PCs, one at work and one at home. They both run under NT4, SP3 and I use VB6 Enterprise on both and yet the VB IDE behaves differently! I also don't use SourceSafe on either PC. Here's the problem. At work when a module is read-only, I can still edit it in the IDE. When I want to save the changes all I need to do is to first change the read-only property. At home however if the module is read-only, the IDE won't let me make any changes to it and I get the "Can't edit module" error message. Does anyone have any idea why this happens?

And you've never had SS on your machine at all - ever?

Do you get the "Locked" icon on the file in the IDE - like in SS?

[Edited by crispin on 09-26-2000 at 12:27 PM]

Good point. I just checked and at home (where I have the problem) when I create a new project I get an "Add project to SourceSafe" message to which I always reply "No". At work I don't get the message, so I guess I don't have SourceSafe installed there. I'm going to see if I can uninstall SourceSafe at home and see if that makes the difference. Thanks.

Yes, I see the "locked" icon in both places.

crispin: I went to Add-Ins>Add-In Manager>SourceCode Control and tutned off all the "Load Behavior" options, and that corrected the problem. Thanks again!

Just a quick addendum:

This problem annoyed the hell out of me for ages when using sourcesafe.

The reason this happens is that when you run the project, VB tries to remove any subs that don't have code in them, and if they are locked, then you get the message. But you've still got to manually search the files to see which one it is, or block checkout (which is no mean feat if you are working on a project group that contains > 30 dlls, ocx's etc.)

- gaffa

Marty, when you move files from one PC to another, just get rid of this file: mssccprj.scc (SourceSafe Status file).

This way on the other computer even if you have SourceSafe installed, you'll be asked to add this project to SourceSafe again, you can reply NO to that and your project will continue to work.

Serge, my experience is that that doesn't work. Even if you delete the file and then say "No" when you start, you can't edit locked modules. Also the scc file is recreated every time.

Yes, that's correct scc file would be created automatically, but... the reason you still cannot modify file is because when the file was released to the SourceSafe it became read-only. So all you have to do is change the attribute of that file and it will be accessible again.

Regars,

Serge, the solution that I arrived at from the suggestion from crispin which was

Quote:

---

I went to Add-Ins>Add-In Manager>SourceCode Control and turned off all the "Load Behavior" options, and that corrected the problem.

---

is preferable to me. Thanks anyhow.