Prompt to select certain fields to show on a report

[skooterboy]

Hi All,

So far, you have all been so much help for me and I thank you

So, here's my dilema:
I have a report (based on a query) that shows Store number, City, State etc, followed with Field1, Field2, Field3 etc. Pretty simple stuff so far.

What I'd like, is when the user runs this report, they will get a prompt enabling them to choose which fields they want to show in the report.

For example, I always want Store number, City & State to show.
However I may only want Field1 & Field3 to show up and not show Field2. The next time I run the report, I may only want Field2 to show up.

Is this possible? I don't want to have to create multiple reports for the different variations.

Any help is much appreciated.

Tim

 

[vbaInet]

I have a report (based on a query) that shows Store number, City, State etc, followed with Field1, Field2, Field3 etc.

What does etc mean here? How many other fields do you have named FieldX? And why have you adopted such a naming convention?

I'm beginning to think that you may have normalisation problems.

 

[skooterboy]

Hi vbaInet,

Sorry, I didn't come here to be insulted.

Let me put this in more simple terms. I have a report that contains 10 fields. I would like a prompt to appear that will let me select which of those 10 fields I'd like to show on the report.

 

[vbaInet]

Sorry, I didn't come here to be insulted.

Where is this coming from? If I was known for insulting people don't you think I would have been banned from here.

Are the fields actually named FieldX or you used that for demonstration purposes only? Are the data types of the fields the same? And if they are, what data types are they?

 

[skooterboy]

Sorry if I misunderstood, but I took "you may have normalisation problems" as an insult to my intelligence.

I used "Field1, Field2" as examples.

 

[melissa_may1]

Hi Skooterboy!

I'm not sure if the term "normalization" is understood in this context.

If you have ten fields in each row, those ten fields should probably be in another table instead, and linked to the table with "Store number" and likely using the Store number as the key.

That way you can have a query that pulls the Store info, and also pulls the Field1, Field 2... data as well.

This type of design is more consistent with relational database design, and would be called a "normalized" design.

It certainly didn't sound like an insult, though, just a comment on the database design itself...

The problem with the design you have is that you now (and probably in the future with other forms and reports) have to use some tricks to retrieve the data you want. Had the database been designed differently ("normalized") then you wouldn't have to work so hard with this report!

(By the way, don't you just hate it when you ask a question, and the discussion centers around what you "should" have, rather than what you "do" have?!!)