Future of Access (1 Viewer)

Source control is only part of the problem. I don't know how this tool works, it's been years since I last tried a source control addin. At that time, the process was abysmally slow but more important was that you had to remember to "check out" BEFORE you started modifying an object. Modifying an object should have automatically initiated the "check out". If you don't "check out", your changes didn't get logged. I would hope that newer versions are better.

The real issue is that if Bob makes a bad change and checks it back in, I may not be able to work on my piece if Bob's change broke something I needed.

Working as a team requires a build manager and the build manager should be the only person who can check objects in and he has to thoroughly check them as well as all other objects before the new changes can be incorporated into the current build.

I've tried a few times to have other developers work on isolated objects and that can work but again, you need one person who incorporates changes made by any team member. That meant me in all the times I tried this method since who can afford an extra developer who just handle's the build?
Using Git Hub, Bob is working on a fork as are you, there is no checkout. The changes are merged back into the main after testing and can always be rolled back.

I am working with a large FE, the add-in exported the original in a matter of minutes, changes take seconds. After working with source control I have been refactoring the code in a more vertical orientation to work better with side by side comparison.
 

Users who are viewing this thread

Back
Top Bottom