report only prints first page of tab control

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have saved a form as a report. The problem I am having is with both the
form and the report. My form is a multipage form, I am using tabcontrols.
When I select the record to print it, I only get the current page. I saved
the form as a report. It only shows the first page in print preview. I can
get it to print the next page when I go to design view and select the next
page. I am sure this is something simple that I have overlooked in the setup.
I just can't find whatever goofup i have done. any help will be appreciated.
 
Jeanie,

Although it is theoretically possible to save a form as a report, I
imagine this would only work relatively smoothly with a simple form
structure. I have never tried saving a form with tab controls as a
report... because I wouldn't expect it to give the results I need. I
would suggest designing your report from scratch, as a report, that way
you have control over how you want it to come out.
 
Steve,

Thank you for your response. I will do that. My form has two subforms and
I need to put it all in one report. The users will need to put in a customer
ID and print the report. When I try to do a query, I get a too many fields
defined error. As I am sure you can tell, I am not an Access person. I do
networking. Everything I have done so far has all fit on one page and I have
been able to use the wizard to do everything.
Thanks,
Jeanie
 
Jeanie,

It looks like the degree of complexity of your project has exceeded the
purposes for which the wizards are applicable. This is normal :-)

Reports have a Sorting and Grouping facility, which often achieves a
similar purpose to subforms in a form scenario. In other words, where
you have a subform doesn't necessarily mean a corresponding subreport,
in fact it seldom does.

But the "too many fields" is a worry... it probably means your table
design is not the best. There will be plenty of help offered here if
you are interested in exploring that aspect.
 
Steve,

The degree of complexity of my project has exceeded the purposes for which I
am applicable as well. My table design is aweful. I have three tables when
I am sure I need a lot more. I think I would still have the same problem
though. I have about 300 fields from these three tables that need to
eventually be compiled into a report somehow. At some later point they want
to add more to this. Arrgh! They will have to employ someone else for that
though. This is for a construction company that needs to be able to take all
the selections their customers make for their new home and keep track of them
and they want to be able to print it out in one report and have the customer
sign off on it. I can't get all the information into the report without
using tabcontrols and subreports. I still have the same printing issue.
 
Jeanie,

No, you are not right here. If you fixed the table design, you would
not still have the same problem. Your statement: "At some later point
they want to add more to this" is a dead giveaway! You mean more
items/categories/types/selections, right? This should be records, not
fields. Regardless of the number of tables required, I feel certain
that all the data you need for your report should require much, much
less than 300 fields. If you would care to give some examples of your
existing fields and data, I (or soemone) can comment more specifically.

If you want to persist with the existing data structure, then I agree,
you will need to use subreports. Not tab controls, these will not
really be helpful for your report.
 
Steve,

Ok, I am not even sure what I need or what can be done anymore. forgive me
for I am being a lot daft. I have slept 7 hours in the last 3 days. For
each home owner I have the subdivison, lotnumber, their name, phone #, cell
#, existing address, dimensions of the house, porch and deck, square footage,
how much is heated and what is not, the maufacturer, color, model or style
number of the exterior and interior paint, trim, roffing, siding, vinyl,
tile, appliances, cabinets, molding, counters, fireplace, faucets. Every
little detail you can possibly think of when building a new house from the
ground up. They want to be able to click a button and get a print out of all
that for the homeowner they select.

jeanie
 
Steve,

i really do appreciate all the help!(: I will keep playing with it and see
what I can come up with.

Jeanie
 
Jeanie,

Probably I would need more details with examples to be definitive here.
But the skeleton concept here is:

Table: HomeOwnwer
HomeOwnerID
Subdivision
LotNumber
HomeOwnerName
Phone
....etc

Table: SelectionItems
ItemID
Item

The data in this table will look like this...
ItemID Item
1 Dimensions
2 Porch
3 Roofing
... etc, down to 300+

Table: HomeOwnerSelections
SelectionID
HomeOwnerID
ItemID
Description
 
Steve,

You are on the right track of what I have. Can I e-mail you a zipped copy
of what I have? Then you can see what I have made. I dont seem to have done
anything right from the beginning and have just made a mess of everything.
Then maybe you could make a suggestion of whether I just need to scrap this
and give up or if it can be saved.

Jeanie
 
Jeanie,

I would be happy to have a look at what you've got. Just remove the .ns
from the end of my return email address.

However, I can tell you without looking that if you want to go down the
track of a proper database design, it will almost certainly be quicker
and easier to start again, rather than try to patch up what you have
done so far. I know you have put a lot of time and sweat into this, so
it is hard to put it down to a learning experience. But the person who
comes after you will sure not thank you for basing the project on a
glorified spreadsheet. Still, it's up to you, and I imagine it is
possible to jack up a report out of the existing structure.
 
Jeanie,

I have looked at your database. I can confirm my earlier
recommendation, namely that it would be better to re-design your tables,
along the lines I suggested before, set your data entry forms up as
continuous view forms, and re-build the report from scratch, as a
report. By the way, if you use a smaller font, and put the controls
closer together, you will get a more efficient interface :-) A change
to my earlier suggestion, would be to include another field, let's call
it Category, in the SelectionItems table, to enable the selections to be
classified e.g. Metal Selection, Deck, etc. I am sorry to say that
this, in my opinion, will be easier than trying to derive a workable
report from the existing data structure. Hope this is helpful. Good luck!
 
Back
Top