Report Parameter Prompt

[leamas]

I'm still very much in the learning stages-



I'm attempting to prompt the user of my database with a parameter for "unit location" when opening a "unit report". Currently, it prompts for "item number", "condition" and "description" when the report is opened. I do not have any macros for opening the report.

In design view, these fields share the property of having a green triangle in the top left corner. I'm assuming this is what causes the prompt? Am I mistaken in this?

Is there a way to assign this property to another field, which is "unit location" as stated above?

Thank you all, appreciate any help.

Regards,

Leamas

[pbaldy]

If you click on the control you should then get a popup you can click on to get the actual issue. My guess is that they are invalid control sources, which will throw the parameter prompt (which is Access saying "I don't know what this is").

[leamas]

If you click on the control you should then get a popup you can click on to get the actual issue. My guess is that they are invalid control sources, which will throw the parameter prompt (which is Access saying "I don't know what this is").

I think this is exactly what I want though, which is to be prompted for a 'value' before running a report. How can I get Access to say "I don't know what 'Location' is?"

Thanks for your help pbaldy

[pbaldy]

Type in anything as the control source that it won't understand. If it's not prompting, then you must be using an existing field name or something. Can you post the db here?

[leamas]

Type in anything as the control source that it won't understand. If it's not prompting, then you must be using an existing field name or something. Can you post the db here?

Ok I see exactly what you are saying. Unfortunately I'm not able to post the db. Do you have any suggestions on the best method for running a report based on the asset's location? As opposed to a report that lists all locations and all assets within the location?

Thank you!

[pbaldy]

Typically either basing it on a parameter query or this type of thing:

BaldyWeb wherecondition

I never use the parameter prompt; I always have the user enter the criteria on a form. You have more control that way. Generally speaking, if a query/report will always be filtered by something, I'll include a criteria in the query. If a filter will only be used sometimes, I'm more likely to use the wherecondition method in the link. I actually just created a report that uses both techniques. It will always be filtered to a date range, so that's in the query. Sometimes they want to be able to filter by driver, so that's in the wherecondition when needed.

[leamas]

My forms are autopopulated with all that unit's details, by entering the criteria "unit #", so what would this other form look like would you suggest?

[pbaldy]

It would have controls (text box, combo box, etc) for whatever criteria were required for the report, and a button to run it.