SpellAndShield Posted June 9, 2010 Share Posted June 9, 2010 What do they do? Do you check in first, then check out? Other way round? I have no idea... Link to comment Share on other sites More sharing options...
chibievil Posted June 9, 2010 Share Posted June 9, 2010 when it checked in you can't edit, but when it checkout you can edit to your hearts content. i have no idea what it means when u give to other people as a dazip or override. Link to comment Share on other sites More sharing options...
nezroy Posted June 10, 2010 Share Posted June 10, 2010 check in/check out are standard concepts from the version control world. The toolset has this functionality so that you and several other people could all be working in the same database w/o trampling on each other's work. You check out an item to work on it and then check it back in when finished. That way other people would know you had it open for editing/were done making changes. When working yourself it's kind of pointless. The DAZIPs are generated from you local copy where needed so you really never have to bother if you don't want. However you should check in everything before creating a builder-to-builder package or if you are trying to backup your projects by backing up the database, since the changes in your local copy are not stored to the DB version until you do a check in. Link to comment Share on other sites More sharing options...
Recommended Posts