Adding forms on tab control

[Dee]

I have a form which contains basics of a customer's order from table
[CustMain].

I placed a tab control on this form which is still empty. I'm trying
to design a project management database and would like to enter one
form for each sub project on each tab page.

[CustMain]

[Financial] [Survey] [Framing] [Siding] [Windows] [Roofing] ...=>

I have all the sub project forms designed. Each time I try to enter
one of them onto a tab page, they don't work. I have tried to copy and
paste the fields but then don't know how to hook them up to their
source data(table or query). Is it possible to do this and then
somehow point them to a source table or query? Could someone either
give me specifics on how to do this or where to go for specifics?

I have tried inserting them as sub forms, but then they display in
datasheet format. I need to these sub project pages to look like the
individual form I designed.

Under what circumstances is it best to use tables instead of queries
as a data sources for forms. My application will have only about 300
orders per year. Each sub project has an average of 45 fields.

[Deano]

Dee wrote:

I have a form which contains basics of a customer's order from table
[CustMain].

I placed a tab control on this form which is still empty. I'm trying
to design a project management database and would like to enter one
form for each sub project on each tab page.

[CustMain]

[Financial] [Survey] [Framing] [Siding] [Windows] [Roofing] ...=>

I have all the sub project forms designed. Each time I try to enter
one of them onto a tab page, they don't work. I have tried to copy and
paste the fields but then don't know how to hook them up to their
source data(table or query). Is it possible to do this and then
somehow point them to a source table or query? Could someone either
give me specifics on how to do this or where to go for specifics?
These steps work for Access 2000; don't know about other versions (always a
good idea to post which version you are using).
Make sure the Control Wizards icon is clicked on in the Toolbox toolbar.
Use the Subform/Subreport control. Drop this onto the page of your tab
control. The subform wizard will run and you can tell Access how the
subform will get it's data.

The Access web has good info on subforms and referencing them in code.
http://www.mvps.org/access/

I have tried inserting them as sub forms, but then they display in
datasheet format. I need to these sub project pages to look like the
individual form I designed.
You have to add them as subforms. The Default View property in the Format
tab of each form allows you to control whether it's displayed as Continuous,
normal or datasheet.

Normally inserting a subform implies that you are displaying child records
in the subform which are related to the parent records of the main form.
Access help should explain this in more detail.
Under what circumstances is it best to use tables instead of queries
as a data sources for forms. My application will have only about 300
orders per year. Each sub project has an average of 45 fields.

It depends. Once you've normalised your data you may find that the data you
require for a form is spread over a number of tables. The only way to piece
this together is by using a query and using this as the datasource.
OTOH a simple database may just need one table.

So make sure you have normalised your tables first.

hth
Martin

[Rick Brandt]

"Dee" <wo********@comcast.net> wrote in message
news:35**************************@posting.google.c om...

Answering my own question

Subform must be based on an existing form. If the source is a table or
query, the the resulting display seems to always result in datasheet
view. This seems to be the case even when datasheet view is disabled
and only form view is chose in properties for the subform. I don't
know if this is a bug in 2k, but hope others will find this info
useful.

A subform *control* is merely a container on a form that points to another form. So
yes, you have to have an existing form for the control to point at. Not a bug.