Curtis Scoville wrote in message <[EMAIL PROTECTED]>... > >Our development team is currently planning the layout for an app that has >30+ forms. We are debating how many c files and segments to have and how to >best organize the project to allow for 3+ developers to share the work >without stepping on each others toes too much. > >Any suggestions? On the one hand we could have a src file for every form, >but that seems excessive. We are also considering the possibility of >creating logical or functional groups of forms that would share a src file >for each group, such that the total number of c files (not including >database files) would be kept to 3 or 4. > >I have reviewed the documentation regarding multi-segmented apps, but I >would appreciate the voices of experience on this matter of splitting up our >code between src files, and a heads up on any challenges we are likely to >encounter is also welcome.
I would like to know just why you think 30 files for 30 forms "seems excessive"? Is it just that you are afraid of large numbers? Smaller is not necessarily better, especially if you have to wade through huge source files to find what you need because everything was stuffed into only 3 files. The answer to the question of how many files you should use is similar to the answer to the question of how long your legs should be. Your legs should be long enough to reach the ground. You should use as many files as you need to get the job done. Now ... isolating one -function- per file might be getting a little excessive. But one (non trivial) form per file is a very useful way of breaking up the work. -- -Richard M. Hartman [EMAIL PROTECTED] 186,000 mi/sec: not just a good idea, it's the LAW! -- For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
