
Signature
Wayne
Manchester, England.
> Hi guys. I'm still quite new to access and I kinda need some help on this. I
> made a form containing a tab control at the bottom. There's 3 pages to this
[quoted text clipped - 9 lines]
> Is there a way whereby I can search the records at the Main form and it's
> reflected on the tab page in the subform? I hope someone can help me on this.
Oh ok. The reason i'm using several forms is that I'm required to have quite
a number of fields.
Can you give me suggetions on how I can make it more simpler? Perhaps using
less forms. Any sample designs I can look at?
> Hi
>
[quoted text clipped - 24 lines]
> > Is there a way whereby I can search the records at the Main form and it's
> > reflected on the tab page in the subform? I hope someone can help me on this.
Arvin Meyer [MVP] - 31 Jul 2007 19:10 GMT
Before trying to solve your problem, I suggest to buy and read a book on
database design. I can recommend:
Database Design for Mere Mortals by Michael J. Hernandez
It is very rare that any useful table has more than perhaps 30 fields. Most
of mine have 5 to 10 fields. Although by no means perfect, the Northwind
sample database that comes with Access is a design start for you to look at.

Signature
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com
> Oh ok. The reason i'm using several forms is that I'm required to have
> quite
[quoted text clipped - 40 lines]
>> > reflected on the tab page in the subform? I hope someone can help me on
>> > this.
John W. Vinson - 31 Jul 2007 19:26 GMT
>Oh ok. The reason i'm using several forms is that I'm required to have quite
>a number of fields.
How many fields in your widest table? I fear you may have fallen into the trap
of "committing spreadsheet"; if you have fieldnames like January, February,
March or Agent1, Agent2, Agent3 etc., you may be on the wrong track.
Designing your table structure to match a paper form will almost surely give
you an *extremely badly normalized* table! It's much better to create
tall-thin, properly normalized tables and adapt the form to them rather than
vice versa!
John W. Vinson [MVP]