I understand that this most likely is a problem with VB6 rather than Vault, but here goes. VB6 allows making changes to Data Environment even when that file is not checked out. The unpleasant scenario goes like this:
I work with the project and make changes to Data Environment, without noticing that it's not checked out
In the end, I try to save everything, and that's when I receive error message, because the file is read-only
In order to save the d.e. file, I check it out. It gets checked in without any warning; it's then reloaded in the project, so I have just lost the changes I made.
I then have to redo the changes.
Edits of not-checked-out file in VB6
Moderator: SourceGear
Edits of not-checked-out file in VB6
Vadim Rapp
This is not a problem with VB6 itself, really, but with the Source Code Control add-in. If you unload the Source Code Control add-in, you will find that you can edit any file that is read-only on disk.
The add-in tries to help make sure you check files out, by blocking edits of read-only files. But it doesn't cover the code editor window in the Data Environment designer, as you discovered.
If you check out your file using Tools->SourceGear Vault->Check Out (instead of right-clicking in the Project Explorer), you can set the Overwrite option to "Don't overwrite/merge later". This might help avoid losing your changes.
If not, you would have to copy your changes to Notepad, check out the file, then copy your changes back (obviously, this wouldn't help with your connection and command definitions, only with the code).
Regards,
The add-in tries to help make sure you check files out, by blocking edits of read-only files. But it doesn't cover the code editor window in the Data Environment designer, as you discovered.
If you check out your file using Tools->SourceGear Vault->Check Out (instead of right-clicking in the Project Explorer), you can set the Overwrite option to "Don't overwrite/merge later". This might help avoid losing your changes.
If not, you would have to copy your changes to Notepad, check out the file, then copy your changes back (obviously, this wouldn't help with your connection and command definitions, only with the code).
Regards,
David Thompson
JELD-WEN, inc.
JELD-WEN, inc.