Too many fields in a report

[wisni1rr]

I am have a report that has too many fields.

The fields I need to display in the report are all required and they take about 277 fields to create.

I can acheive the desired result by calling subform(s) if I am not mistaken. (correct me if I will still be limited on my fields) However, I need each of the subforms to pull data in regards to my paramater query on my main report. I can acheive this by adding the paramater field in each subform but then it will ask the parameter for every subform on my report. Is it possible to make it so I only ask the parameter once?

The report is serving as a complete listing of an entry in my database. (seperate but 1to1 linked tables linked by the main table AutoNumber)

[Rabbit]

I seriously think you need to reconsider the design of the report. I can't think of any reason anyone would need to see 277 fields all the time all the way across. How would they even manage it? And that's not to mention the overhead of running and rendering such a report.

[wisni1rr]

The report is in regards to real estate. It describes the property in full detail. It fits to a legal 8.5" x 14". It contains various data related to the property such as room dimentions, heating, layouts, legal information, sale, information, exterior conditions, and more.

This report will generally be used to reflect one complete record set.

I included a sample pic.

Thanks you for taking the time to help Rabbit.

I tried making a section into a subform and it works as desired. However. I have to enter my parameter query answer twice. Is it possible to make it so the paraent parameter setting will be adopted by the child subfrom?
[imgnothumb]http://bytes.com/attachments/attachment/5704d1322137911/sample.jpg[/imgnothumb]

[Rabbit]

Not that I know of. However, you could create a form where the user enters in the required values and then the report can reference the controls on the form.

[NeoPa]

You can link subforms to their parent data by specifying the Link Child Fields and Link Master Fields properties, but this won't necessarily ensure there is no need for the value to be prompted again.

[Mihail]

Just an idea:

Declare all parameters as public variables, set the values from the main form and use it where you need.

[wisni1rr]

Mihail,

That sounds like it could work. Can you provide an example?

[NeoPa]

That may work for you, but I should warn you it is a clumsy approach that will lead to further complication down the line.

An appreciably more sensible approach would be to recognise the wisdom of post #4 by Rabbit. It really isn't a good idea in a proper project to be using parameter queries at all.

[wisni1rr]

I'm not completely sold on a parameter query if it is not needed. I am using the report to display a complete record of a property. Their are several tables which are joined by a 1:1 relationships. I just need to list all the fields on a single (printable) report. Currently it is set up as a parameter query which asks for the Primary key (BWA_ID).

In regards to Rabbit in post#4. I don't quite understand. I have a form that has all the controls on it that would be used in the report(Input Form). I don't understand how this would solve my too many field issue.

Thanks for your help as always.

[NeoPa]

It means you don't need to use parameters. This is what the question of this thread is (See post #1). If you need help with anything else then you should ask for it in a thread for that new question.

[Mihail]

Hope you can use that (see attachment) to reduce the fields number in your report by replacing with text boxes.

Good luck !