fmoore0001
Programmer
For the first time I need to work on a project with multiple programmers. I have found that Project Files do not allow multiple users. So, how do you guys get around the problem?
Frank
Frank
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Multi-use of a Project File
- Thread starter fmoore0001
- Start date
- Status
Mike Gagnon
Programmer
fmoore0001
I believe you may require Microsoft Visual Source Safe.
Mike Gagnon
If you want to get the best response to a question, please check out FAQ184-2483 first.
I believe you may require Microsoft Visual Source Safe.
Mike Gagnon
If you want to get the best response to a question, please check out FAQ184-2483 first.
One way to deal with this, is to create a project for each developer - it can be "local" and everyone can point at the same files on the network.
Then the developer can change thier copy of the project to point at a local copy any file(s) they are working on.
While this can take some procedures and discipline, it's essentially the way any source control mechanism works - althought that is usually a bit more automatic. Obviously a mechanism needs to be in place to marshal changes made by two or more developers to the same files so they don't "step on" each other.
It wouldn't be hard to create a generic project hook (or even standalone program using the project object) to show the developer which files they have locally. This would eliminate the faulty memory problem.
Rick
Then the developer can change thier copy of the project to point at a local copy any file(s) they are working on.
While this can take some procedures and discipline, it's essentially the way any source control mechanism works - althought that is usually a bit more automatic. Obviously a mechanism needs to be in place to marshal changes made by two or more developers to the same files so they don't "step on" each other.
It wouldn't be hard to create a generic project hook (or even standalone program using the project object) to show the developer which files they have locally. This would eliminate the faulty memory problem.
Rick
- Thread starter
- #4
fmoore0001
Programmer
We found a somewhat simple solution on this issue of multiple project files and programmer for the same program. It seems to work with some simple controls.
1) A basic program is designed with ONE main Prg file and ONE Menu. The PRG has a READ EVENTS Command at the end of the PRG;
2) All menus, programs (functions or procedures), classes, reports, screen and misc. files are stores in directories under the main project directories. All projects, however, are in the project root directory;
3) Any called procedure, function or class is run from the root program or the root menu. The menu itself has no procedures, just submenus and commands.
3) Once a day everyone compiles. Since Foxpro detects the missing files, and seems to know where it is likely at prg, screen, reports, etc. are after a compile or two, using the root prg and root menu, the compiles keep everyone up to date.
It seems to work just fine. Once a day the group checks out the work.
Frank
1) A basic program is designed with ONE main Prg file and ONE Menu. The PRG has a READ EVENTS Command at the end of the PRG;
2) All menus, programs (functions or procedures), classes, reports, screen and misc. files are stores in directories under the main project directories. All projects, however, are in the project root directory;
3) Any called procedure, function or class is run from the root program or the root menu. The menu itself has no procedures, just submenus and commands.
3) Once a day everyone compiles. Since Foxpro detects the missing files, and seems to know where it is likely at prg, screen, reports, etc. are after a compile or two, using the root prg and root menu, the compiles keep everyone up to date.
It seems to work just fine. Once a day the group checks out the work.
Frank
- Status
