Personnaly, I would look at a tool like Visual SourceSafe to share components of a project instead of working on separate projects.

With OOP, you will write most of the code in reusable class that will be used thorough the project, making it very hard to break a project in multiple smaller one.

HTH

>I have a question that I would like some opinions on. We are working on setting up a very big application that several programmers will be working on at one time. Since this application has several large pieces to it we are considering making it two or more different projects with different executables. These would all use the same tables in the same dbc. The first exe would contain a button that calls the second exe and then exiting the second exe would take the user back to the first.
>
>Now the plus side of this is that different programmers can be responsible for different parts of the whole application without stepping on one another while they are working. Also this keeps the application smaller as individual pieces are created rather than one LARGE app. So if something has to be fixed in one part only that part is recompiled instead of the whole app.
>
>We have created similar apps in the FPW 2.6 world but there we would do a scatter and gather between exes so that the information was passed and updated from one app to another.
>
>What would be a VFP OOP solution to this kind of environment setup? I would be very interested to hear if anyone else has taken this kind of approach and what were the pluses and minuses involved.