I’m having several problems with team coding and SQL Navigator 6.0. My whole team has similar issues. We weren’t having this problem with versions 5.x.
Here are the issues the best I can remember them now:
a) Every time we check in database code, we always get the message that the code has changed and must be saved prior to check in. This happens even if we JUST saved the code to the database. This is annoying
b)A more serious problem I just encountered has to do with new packages. I’ll create a new package, and then when I save it, it saves the package spec fine and then, as it saves the body it says that it is creating the Microsoft VSS entry/library/whatever for that file so that it is in source safe. This process hangs up SQLNav for a long time and then, when it is done, I can’t even edit the package body (as if someone else has it checked out). When I look in the Team Coder Viewer, it says I have it checked out so I undo the check out. I then get all the way out of SQLNav and then open up VSS and try to delete the entry so I can just start over and I get a message that this can’t be done because the file is open.
I am looking into it but could not reproduce your issue here yet using Visual SourceSafe as well. Will keep you posted wit h more updates next week. Hope that we can provide you a 6.2 Beta build soon with the the fix.
We have fixed issue (a) as reported. It will be available in the next Beta build which will be available very soon. Please check the next Beta build out and let us know if you are happy with the changes.