Enter Parameter Value?

[OlBill]

I keep getting an "Enter Parameter Value" Message when I open a report. If I click "Ok", it opens and shows the correct values. This is the only field I'm having this issue with. I've checked and compared, and I set them all up the same way.
Help would be appreciated.

[Welshgasman]

And you cannot say what that parameter is?

[OlBill]

And you cannot say what that parameter is?

I need them all if I understand your question correctly.

[OlBill]

If I need a certain phase, I go into the query. Other than that, I don't want it to ask. It's not asking me for any of the others. Also, If I put a phase in the parameter box, it gives me back all of them.

[Welshgasman]

Why do you have combos in a report?
It is not like you can select anything else?

You have a field somewhere called Current Phase NOT CurrentPhase.

I have been unable to find it yet?, perhaps you might know where you placed it?

[OlBill]

Why do you have combos in a report?
It is not like you can select anything else?

You have a field somewhere called Current Phase NOT CurrentPhase.

I have been unable to find it yet?, perhaps you might know where you placed it?

So it shows the names and not the numbers. Is that not the right way to do it?

I've looked at the table, the form and the query, I don't see it either.

[Gicu]

It was in the two count text boxes on the upper right; change them to use CurrentPhase instead (and changed the text to the actual numeric values).

Cheers,

[OlBill]

It was in the two count text boxes on the upper right; change them to use CurrentPhase instead (and changed the text to the actual numeric values).

Cheers,

Many thanks!

[Welshgasman]

Yes, found it, after I took a break for dinner.

=Count(IIf([Current Phase]="Meridium",True,Null))

I would get rid of the combos?, I do not see where they would be useful.?
I just bring in that data into the query, which is what I did for the CurrentPhase combo, which I amended to a textbox.

[Gicu]

I actually use combos in the reports for the exact same reason, I don't have to add all the tables to the report's record source, just get the combo display the description instead of the numeric value. I wouldn't say it is right or wrong, just one's preference...

And in the forms doing the same thing makes a huge difference, many times being the main decider if a form is updatable or not.

Cheers,

[Welshgasman]

I actually use combos in the reports for the exact same reason, I don't have to add all the tables to the report's record source, just get the combo display the description instead of the numeric value. I wouldn't say it is right or wrong, just one's preference...

And in the forms doing the same thing makes a huge difference, many times being the main decider if a form is updatable or not.

Cheers,

I was referring to the fact they do not come up as combos?, but valid point all the same.
For myself, I have always put the data into the source. I have no real need these days, but I will bear it in mind. I have used buttons though.

[OlBill]

Thanks fellows. Much appreciated.

[OlBill]

I actually use combos in the reports for the exact same reason, I don't have to add all the tables to the report's record source, just get the combo display the description instead of the numeric value. I wouldn't say it is right or wrong, just one's preference...

And in the forms doing the same thing makes a huge difference, many times being the main decider if a form is updatable or not.

Cheers,

I've been thinking about this using combos in the report thing. Is this socially unacceptable? Union queries is the other way, correct? I tried that yesterday and don't see the advantage?

[Welshgasman]

I've been thinking about this using combos in the report thing. Is this socially unacceptable? Union queries is the other way, correct? I tried that yesterday and don't see the advantage?

No, just that I asscociated combos with interaction with the user.
@Gicu advised that is saves linking in extra tables at the source.