Lookupform(s) (correction!)
in [General]
|
Prev: Adding "°" symbol to numbers
Next: MS says that all tables should live in SQL (for performance reasons)
From: Lars Brownies on 21 Apr 2010 11:23 Oops. I didn't mean lookup forms. I mean control forms, in which the lookup tables are maintained. Lars "Lars Brownies" <Lars(a)Browniew.com> schreef in bericht news:hqn1ji$2cds$1(a)textnews.wanadoo.nl... > I'm in the pre-stage of building an application with about 15 lookup > tables. In stead of building 15 lookup forms, I'm thinking about making > one generic lookup form and changing the record source depending on the > table needed. I would have to add code for validation purposes. > > Is this doable or should I make 15 separate forms? > > Thanks, > > Lars
From: golfinray on 21 Apr 2010 12:00
IMHO, that would not be the way to go. Normally, you might want one mainform and two or three subforms at most. 15 is going to be difficult. What are your relationships between these tables? If you have one-to-one relationships, simply combine the tables. If you have one-to-many, you would need to build maybe 5 forms with two subforms each. -- Milton Purdy ACCESS State of Arkansas "Lars Brownies" wrote: > Oops. I didn't mean lookup forms. I mean control forms, in which the lookup > tables are maintained. > > Lars > > "Lars Brownies" <Lars(a)Browniew.com> schreef in bericht > news:hqn1ji$2cds$1(a)textnews.wanadoo.nl... > > I'm in the pre-stage of building an application with about 15 lookup > > tables. In stead of building 15 lookup forms, I'm thinking about making > > one generic lookup form and changing the record source depending on the > > table needed. I would have to add code for validation purposes. > > > > Is this doable or should I make 15 separate forms? > > > > Thanks, > > > > Lars > > . > |