I think you misread the response then. There was no discussion (here) about code modules to forms, although there was a thread about that yesterday.
The question here was relating to "an array of structs" but then having a separate form for each struct in the array. Presumably, if this is actually an array, then the 40 records all have the same "shape". If they have the same shape, you only need one form and load the data into it as needed. -- -Richard M. Hartman [EMAIL PROTECTED] 186,000 mi/sec: not just a good idea, it's the LAW! Stringer wrote in message <[EMAIL PROTECTED]>... > >Actually I'll take umbrage with the response here. > >I believe that in a GUI environment having one C/C++ module for >each form is a good programming technique. Only minor, related >forms should be supported by the same module. > >Also if your application has a number of forms then don't try and >overlay them unless it is natural for your application. It is far more >efficient for development and maintenance to keep separate forms >separate. > >If your application has 40 forms, then so be it! And then you'd >have a little more than 40 C/C++ modules arranged in multiple >segments. > >Roger Stringer >Marietta Systems, Inc. > >---------------------------------------------------------------------- > >>Subject: RE: Newbie needs help >>From: Logie Urqhart <[EMAIL PROTECTED]> >>Date: Wed, 26 Jul 2000 10:32:41 +0100 > >>I belive there are some design issues you might want to look at. > >>Keep in mind that memory on the Palm is like gold dust... > >>> Here are the program specs: >>> 1) I have an array of structs. Each struct is displayed and >>> edited in a >>> form. So, if there are 40 in the array, there are 40 forms, >>> respectively. > >>Don't have 40 'seperate' forms, the sive of your program would be huge, and >>maintaince would be a nightmare. It would be better to have one generic >>form, and load the data in and out of it, when needed. >---------------------------------------------------------------------- > > > -- For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
