Results 1 to 11 of 11

Thread: [RESOLVED] SourceSafe problem

  1. #1

    Thread Starter
    PowerPoster
    Join Date
    Apr 2005
    Location
    Debug.Print
    Posts
    3,885

    Resolved [RESOLVED] SourceSafe problem

    I added my project to SourceSafe by mistake and now everything is ReadOnly. I cant edit my project files at all. Is there any way to take my project out of SourceSafe and get rid of SourceSafe altogether?

    Please advise.

  2. #2
    Frenzied Member oh1mie's Avatar
    Join Date
    Sep 2001
    Location
    Finland
    Posts
    1,043

    Re: SourceSafe problem

    IF you show with mousepointer modules, forms and Project name, click right button to get menu. There is choice Check Out.
    When you finish editing, then Check module in.
    That's main idea for Scoure Safe, it keep history of your changes
    oh1mie/Vic


  3. #3

    Thread Starter
    PowerPoster
    Join Date
    Apr 2005
    Location
    Debug.Print
    Posts
    3,885

    Re: SourceSafe problem

    so before i can do anything with the project, i have to check it out? then it wont be read only any longer?

  4. #4
    PowerPoster jcis's Avatar
    Join Date
    Jan 2003
    Location
    Argentina
    Posts
    4,430

    Re: SourceSafe problem

    Maybe deleting Sourcesafe files created by sourcesafe, SCC files, in the same folder where your project is.
    You could also remove your app from inside sourcesafe

  5. #5
    Frenzied Member oh1mie's Avatar
    Join Date
    Sep 2001
    Location
    Finland
    Posts
    1,043

    Re: SourceSafe problem

    Quote Originally Posted by BrailleSchool
    so before i can do anything with the project, i have to check it out? then it wont be read only any longer?
    Yes, but when you check in, then it's Read only again.

    I use allways Scource Safe
    oh1mie/Vic


  6. #6

    Thread Starter
    PowerPoster
    Join Date
    Apr 2005
    Location
    Debug.Print
    Posts
    3,885

    Re: SourceSafe problem

    Quote Originally Posted by jcis
    Maybe deleting Sourcesafe files created by sourcesafe, SCC files, in the same folder where your project is
    already tried that and as soon as you open the project in vb6.exe then those deleted files are recreated all over again.

  7. #7
    PowerPoster jcis's Avatar
    Join Date
    Jan 2003
    Location
    Argentina
    Posts
    4,430

    Re: SourceSafe problem

    Quote Originally Posted by BrailleSchool
    already tried that and as soon as you open the project in vb6.exe then those deleted files are recreated all over again.
    Open Sourcesafe and delete your project from there

  8. #8
    Frenzied Member oh1mie's Avatar
    Join Date
    Sep 2001
    Location
    Finland
    Posts
    1,043

    Re: SourceSafe problem

    After that, open explorer and select your files,open properties and uncheck read only attribute.
    oh1mie/Vic


  9. #9
    MS SQL Powerposter szlamany's Avatar
    Join Date
    Mar 2004
    Location
    Connecticut
    Posts
    18,263

    Re: SourceSafe problem

    Source safe is good - you should use it.

    To correct what you have done simply CHECKOUT all the files. Go into SOURCE SAFE - select all the files - CHECKOUT.

    That turns off the read-only.

    You never have to check them in again if you do not want to. But you should check them in every day and check out the next day. That's why a version-tracking package like source safe is so important.

    Why do you not want to use it?

    *** Read the sticky in the DB forum about how to get your question answered quickly!! ***

    Please remember to rate posts! Rate any post you find helpful - even in old threads! Use the link to the left - "Rate this Post".

    Some Informative Links:
    [ SQL Rules to Live By ] [ Reserved SQL keywords ] [ When to use INDEX HINTS! ] [ Passing Multi-item Parameters to STORED PROCEDURES ]
    [ Solution to non-domain Windows Authentication ] [ Crazy things we do to shrink log files ] [ SQL 2005 Features ] [ Loading Pictures from DB ]

    MS MVP 2006, 2007, 2008

  10. #10

    Thread Starter
    PowerPoster
    Join Date
    Apr 2005
    Location
    Debug.Print
    Posts
    3,885

    Re: SourceSafe problem

    Quote Originally Posted by szlamany
    Source safe is good - you should use it.

    To correct what you have done simply CHECKOUT all the files. Go into SOURCE SAFE - select all the files - CHECKOUT.

    That turns off the read-only.

    You never have to check them in again if you do not want to. But you should check them in every day and check out the next day. That's why a version-tracking package like source safe is so important.

    Why do you not want to use it?
    It's not that I don't want to use it. Just that I didn't know how to use it, hahaha. Now that I kinda understand it, maybe I should use it.

  11. #11
    MS SQL Powerposter szlamany's Avatar
    Join Date
    Mar 2004
    Location
    Connecticut
    Posts
    18,263

    Re: SourceSafe problem

    It is so nice to be able to right-click a file in SOURCESAFE - show history - see every moment it was checked in and out - and even do a quick DIFF display on two different versions. It's very important to us.

    *** Read the sticky in the DB forum about how to get your question answered quickly!! ***

    Please remember to rate posts! Rate any post you find helpful - even in old threads! Use the link to the left - "Rate this Post".

    Some Informative Links:
    [ SQL Rules to Live By ] [ Reserved SQL keywords ] [ When to use INDEX HINTS! ] [ Passing Multi-item Parameters to STORED PROCEDURES ]
    [ Solution to non-domain Windows Authentication ] [ Crazy things we do to shrink log files ] [ SQL 2005 Features ] [ Loading Pictures from DB ]

    MS MVP 2006, 2007, 2008

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width