D
Damon Heron
Hi all:
A friend and I are co-developing a db and we primarily correspond by email
and send our code revisions back and forth. What is the best way to handle
keeping track of changes and making sure that we don't screw up each other's
programming efforts with changes we have made? We have a Access template db
called "Issues", where you put in work assignments, but is there a better
way to keep track of progress? I have suggested a 2-step process, where we
work on the db and name it with our initials and own version number, then at
weekly intervals, merge the two versions into a new complete version, test
it, and if it is working properly, continue with the new merged version as
our new starting point. My partner doesn't think this is a good idea. He
is suggesting some bug tracking software, but I am not sure how this would
help us with Access.
Any ideas would be appreciated.
Thanks!
A friend and I are co-developing a db and we primarily correspond by email
and send our code revisions back and forth. What is the best way to handle
keeping track of changes and making sure that we don't screw up each other's
programming efforts with changes we have made? We have a Access template db
called "Issues", where you put in work assignments, but is there a better
way to keep track of progress? I have suggested a 2-step process, where we
work on the db and name it with our initials and own version number, then at
weekly intervals, merge the two versions into a new complete version, test
it, and if it is working properly, continue with the new merged version as
our new starting point. My partner doesn't think this is a good idea. He
is suggesting some bug tracking software, but I am not sure how this would
help us with Access.
Any ideas would be appreciated.
Thanks!