Database Design

[lloydmav]

I'm after a bit of professional advice here. I've just been handed over a design specification and an interface and have been asked to build a very big database. The interface is made up of one form with about 12 tabs on it. I was wondering whether I could set up each tab to a different table or whether I should change the design and have a form for each table. There are also currently a number of subforms on most of the tabs.

Does anyone have any views or recommendations?

Thanks for any help

Lloyd

 

[DES]

Personally

I have always liked working with the Tab design that you are speaking of. However with too many tabs based on queries and implimenting after update events and requeries the design can really be slowed down.

What I mean is that if you have something going on on tab one and by doing that something it updates or requeries something on tabs two three and four causing them to requery or recalc then it slows the whole thing down.

I guess it is just easier to say too much of a good thing is not good. Frequently I have seen too much of forms and sub forms on different tabs slowing the style down. Done properly it is good but add a lot of coding and it can really bog down.