i'm new to visual basic. i've been asked to modify a visual basic application, but my problem is when i try to edit one of the modules, i get a message that it cannot be edited.
It's probably been made read only so that changes can be controlled by the source owner/administrator. I think you should talk to them before you do anything.
Has the vb project been added into sourcesafe? If so then you will need the sourcesafe application - then you will be able to "check out" the module for editing. You will hae to talk to the source owner about that.
if the project hasn't been added into sourcesafe you can do a "right mouse" on the module through internet explorer and select properities you can check to see if the "read only" attribute has been checked.
it wasn't me either who gave tomkane a star, but i'm giving you one for a more detailed explanation.
well back to my problem, pls forgive me if i ask too basic questions for all the members of this thread. i'm more into visual foxpro than visual basic.
here it is. everytime i open the project i'm asked to enter a user and password for the sourcesafe. when i try to click the browse button, i'm being asked to locate the "srcsafe.ini". since i don't know the user and password, i just clicked "cancel".
The project has been added to SourceSafe - you will need the username and password of the source owner.
________________________________________________________________
If you want to get the best response to a question, please check out FAQ222-2244 first
'People who live in windowed environments shouldn't cast pointers.'
R17 -
Like johnwm says, you'll need to have an ID & password for the SourceSafe database so that you can check the code out for modification. When you do this, VSS will copy the source code to your working directory (defined at the project level in VSS) and remove the read-only flag.
After you've finished with your changes, you'd then check it back in to Source Safe so that other people can see/use your changes. VSS will update it's copy of the source code, and mark the source files as read-only again.
I have had the read-only thing happen. The cause was burning the projects onto CD's, flying across the continent, then loading the code onto another machine. The CD burn changes everything to read only and the attibute stays after copying to a hard drive. It was a BIG project and a major pain to change all of the attributes back to Read/write.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.