Parameter Values for Criteria Not Set?

[Guest]

Hi Everyone.

I set up a report based on a query, where the user is prompted to enter
the start date and end date, which works great. However, why would some
of my other fields also prompt users to enter criteria? I set no criteria for
any other fields.

After user enters the date range, the report is asking for a [CostPerFoot]
parameter. I've checked the query parameters on the [CostPerFoot] and it's
set to
currency (in the report, query and table).

If I run the query only, it runs perfectly. Why is the [CostPerFoot]
parameter
showing up for the report??

Thanks for your help!

Karen

 

[Guest]

It could be that you bounded the fields in the Report to the wrong names that
doesn't apear in the query.
Go through the fields and see if they all bounded to fields that apear in
the query.

 

[Guest]

Thank you for replying. I checked all the properties - the report properties
are set for the correct query. As mentioned earlier, the properties are also
set the same (e.g. currency). Any other suggestions?

Thanks Again.
Karen

It could be that you bounded the fields in the Report to the wrong names that
doesn't apear in the query.
Go through the fields and see if they all bounded to fields that apear in
the query.

Hi Everyone.

I set up a report based on a query, where the user is prompted to enter
the start date and end date, which works great. However, why would some
of my other fields also prompt users to enter criteria? I set no criteria for
any other fields.

After user enters the date range, the report is asking for a [CostPerFoot]
parameter. I've checked the query parameters on the [CostPerFoot] and it's
set to
currency (in the report, query and table).

If I run the query only, it runs perfectly. Why is the [CostPerFoot]
parameter
showing up for the report??

Thanks for your help!

Karen

 

[Guest]

I ment, check the properties of the fields in the report and not the report
itself, check if the fields bounded to the right fields in the query

Thank you for replying. I checked all the properties - the report properties
are set for the correct query. As mentioned earlier, the properties are also
set the same (e.g. currency). Any other suggestions?

Thanks Again.
Karen

It could be that you bounded the fields in the Report to the wrong names that
doesn't apear in the query.
Go through the fields and see if they all bounded to fields that apear in
the query.

Hi Everyone.

I set up a report based on a query, where the user is prompted to enter
the start date and end date, which works great. However, why would some
of my other fields also prompt users to enter criteria? I set no criteria for
any other fields.

After user enters the date range, the report is asking for a [CostPerFoot]
parameter. I've checked the query parameters on the [CostPerFoot] and it's
set to
currency (in the report, query and table).

If I run the query only, it runs perfectly. Why is the [CostPerFoot]
parameter
showing up for the report??

Thanks for your help!

Karen

 

[Guest]

I had checked the properties in the field (of the report), everything checked
out OK.
Any other thoughts?

I ment, check the properties of the fields in the report and not the report
itself, check if the fields bounded to the right fields in the query

Thank you for replying. I checked all the properties - the report properties
are set for the correct query. As mentioned earlier, the properties are also
set the same (e.g. currency). Any other suggestions?

Thanks Again.
Karen

It could be that you bounded the fields in the Report to the wrong names that
doesn't apear in the query.
Go through the fields and see if they all bounded to fields that apear in
the query.
On each field you can press on the ControlSource Property and see the list
of the fields, and you can see if you have a match

:

Hi Everyone.

I set up a report based on a query, where the user is prompted to enter
the start date and end date, which works great. However, why would some
of my other fields also prompt users to enter criteria? I set no criteria for
any other fields.

After user enters the date range, the report is asking for a [CostPerFoot]
parameter. I've checked the query parameters on the [CostPerFoot] and it's
set to
currency (in the report, query and table).

If I run the query only, it runs perfectly. Why is the [CostPerFoot]
parameter
showing up for the report??

Thanks for your help!

Karen

 

[Guest]

Remove the field named CostPerFoot from the report and try running it

I had checked the properties in the field (of the report), everything checked
out OK.
Any other thoughts?

I ment, check the properties of the fields in the report and not the report
itself, check if the fields bounded to the right fields in the query

Thank you for replying. I checked all the properties - the report properties
are set for the correct query. As mentioned earlier, the properties are also
set the same (e.g. currency). Any other suggestions?

Thanks Again.
Karen

:

It could be that you bounded the fields in the Report to the wrong names that
doesn't apear in the query.
Go through the fields and see if they all bounded to fields that apear in
the query.
On each field you can press on the ControlSource Property and see the list
of the fields, and you can see if you have a match

:

Hi Everyone.

I set up a report based on a query, where the user is prompted to enter
the start date and end date, which works great. However, why would some
of my other fields also prompt users to enter criteria? I set no criteria for
any other fields.

After user enters the date range, the report is asking for a [CostPerFoot]
parameter. I've checked the query parameters on the [CostPerFoot] and it's
set to
currency (in the report, query and table).

If I run the query only, it runs perfectly. Why is the [CostPerFoot]
parameter
showing up for the report??

Thanks for your help!

Karen

 

[Guest]

Sorry, the field that bounded to CostPerFoot, remove it from the report and
run it

I had checked the properties in the field (of the report), everything checked
out OK.
Any other thoughts?

I ment, check the properties of the fields in the report and not the report
itself, check if the fields bounded to the right fields in the query

Thank you for replying. I checked all the properties - the report properties
are set for the correct query. As mentioned earlier, the properties are also
set the same (e.g. currency). Any other suggestions?

Thanks Again.
Karen

:

It could be that you bounded the fields in the Report to the wrong names that
doesn't apear in the query.
Go through the fields and see if they all bounded to fields that apear in
the query.
On each field you can press on the ControlSource Property and see the list
of the fields, and you can see if you have a match

:

Hi Everyone.

I set up a report based on a query, where the user is prompted to enter
the start date and end date, which works great. However, why would some
of my other fields also prompt users to enter criteria? I set no criteria for
any other fields.

After user enters the date range, the report is asking for a [CostPerFoot]
parameter. I've checked the query parameters on the [CostPerFoot] and it's
set to
currency (in the report, query and table).

If I run the query only, it runs perfectly. Why is the [CostPerFoot]
parameter
showing up for the report??

Thanks for your help!

Karen

 

[Guest]

I found it!! Believe it or not, one of my calculations was messing things up.
On the report, I had:

=([Total Foot Length]*[Cost Per Foot])

This calculated on the report just fine. What I didn't see until now,
was on the report, the code should have been:

=([Total Foot Length]*[CostPerFoot])

translation = {{No Spaces!}}. I didn't have spaces in the name of the
actual field "CostPerFoot", but I put the spaces there inadvertantly, when
I was putting everything together. The not-so-funny thing was that I did
this in a couple of queries!! Which explains why each one was asking for the
same
information.

I removed the spaces and everything works as it should.

Thanks anyway. I appreciate your time.

Karen

I ment, check the properties of the fields in the report and not the report
itself, check if the fields bounded to the right fields in the query

Thank you for replying. I checked all the properties - the report properties
are set for the correct query. As mentioned earlier, the properties are also
set the same (e.g. currency). Any other suggestions?

Thanks Again.
Karen

It could be that you bounded the fields in the Report to the wrong names that
doesn't apear in the query.
Go through the fields and see if they all bounded to fields that apear in
the query.
On each field you can press on the ControlSource Property and see the list
of the fields, and you can see if you have a match

:

Hi Everyone.

I set up a report based on a query, where the user is prompted to enter
the start date and end date, which works great. However, why would some
of my other fields also prompt users to enter criteria? I set no criteria for
any other fields.

After user enters the date range, the report is asking for a [CostPerFoot]
parameter. I've checked the query parameters on the [CostPerFoot] and it's
set to
currency (in the report, query and table).

If I run the query only, it runs perfectly. Why is the [CostPerFoot]
parameter
showing up for the report??

Thanks for your help!

Karen

 

[Guest]

Exactly what I was trying to say, a field that does not exist in the query,
in that case [Cost Per Foot], the report was looking for it in the query,
when it didnt find it, it assume that it is a parrameter.

I found it!! Believe it or not, one of my calculations was messing things up.
On the report, I had:

=([Total Foot Length]*[Cost Per Foot])

This calculated on the report just fine. What I didn't see until now,
was on the report, the code should have been:

=([Total Foot Length]*[CostPerFoot])

translation = {{No Spaces!}}. I didn't have spaces in the name of the
actual field "CostPerFoot", but I put the spaces there inadvertantly, when
I was putting everything together. The not-so-funny thing was that I did
this in a couple of queries!! Which explains why each one was asking for the
same
information.

I removed the spaces and everything works as it should.

Thanks anyway. I appreciate your time.

Karen

I ment, check the properties of the fields in the report and not the report
itself, check if the fields bounded to the right fields in the query

Thank you for replying. I checked all the properties - the report properties
are set for the correct query. As mentioned earlier, the properties are also
set the same (e.g. currency). Any other suggestions?

Thanks Again.
Karen

:

It could be that you bounded the fields in the Report to the wrong names that
doesn't apear in the query.
Go through the fields and see if they all bounded to fields that apear in
the query.
On each field you can press on the ControlSource Property and see the list
of the fields, and you can see if you have a match

:

Hi Everyone.

I set up a report based on a query, where the user is prompted to enter
the start date and end date, which works great. However, why would some
of my other fields also prompt users to enter criteria? I set no criteria for
any other fields.

After user enters the date range, the report is asking for a [CostPerFoot]
parameter. I've checked the query parameters on the [CostPerFoot] and it's
set to
currency (in the report, query and table).

If I run the query only, it runs perfectly. Why is the [CostPerFoot]
parameter
showing up for the report??

Thanks for your help!

Karen

 

[Guest]

Yes, but I had previously looked to verify the fields were there - which they
were,
technically. I just did not catch the typo on the field name when I
previously looked.

Exactly what I was trying to say, a field that does not exist in the query,
in that case [Cost Per Foot], the report was looking for it in the query,
when it didnt find it, it assume that it is a parrameter.

I found it!! Believe it or not, one of my calculations was messing things up.
On the report, I had:

=([Total Foot Length]*[Cost Per Foot])

This calculated on the report just fine. What I didn't see until now,
was on the report, the code should have been:

=([Total Foot Length]*[CostPerFoot])

translation = {{No Spaces!}}. I didn't have spaces in the name of the
actual field "CostPerFoot", but I put the spaces there inadvertantly, when
I was putting everything together. The not-so-funny thing was that I did
this in a couple of queries!! Which explains why each one was asking for the
same
information.

I removed the spaces and everything works as it should.

Thanks anyway. I appreciate your time.

Karen

I ment, check the properties of the fields in the report and not the report
itself, check if the fields bounded to the right fields in the query

:

Thank you for replying. I checked all the properties - the report properties
are set for the correct query. As mentioned earlier, the properties are also
set the same (e.g. currency). Any other suggestions?

Thanks Again.
Karen

:

It could be that you bounded the fields in the Report to the wrong names that
doesn't apear in the query.
Go through the fields and see if they all bounded to fields that apear in
the query.
On each field you can press on the ControlSource Property and see the list
of the fields, and you can see if you have a match

:

Hi Everyone.

I set up a report based on a query, where the user is prompted to enter
the start date and end date, which works great. However, why would some
of my other fields also prompt users to enter criteria? I set no criteria for
any other fields.

After user enters the date range, the report is asking for a [CostPerFoot]
parameter. I've checked the query parameters on the [CostPerFoot] and it's
set to
currency (in the report, query and table).

If I run the query only, it runs perfectly. Why is the [CostPerFoot]
parameter
showing up for the report??

Thanks for your help!

Karen

 

[Guest]

I'm happy its all OK now, good luck with the project.
Have a great weekend

Yes, but I had previously looked to verify the fields were there - which they
were,
technically. I just did not catch the typo on the field name when I
previously looked.

Exactly what I was trying to say, a field that does not exist in the query,
in that case [Cost Per Foot], the report was looking for it in the query,
when it didnt find it, it assume that it is a parrameter.

I found it!! Believe it or not, one of my calculations was messing things up.
On the report, I had:

=([Total Foot Length]*[Cost Per Foot])

This calculated on the report just fine. What I didn't see until now,
was on the report, the code should have been:

=([Total Foot Length]*[CostPerFoot])

translation = {{No Spaces!}}. I didn't have spaces in the name of the
actual field "CostPerFoot", but I put the spaces there inadvertantly, when
I was putting everything together. The not-so-funny thing was that I did
this in a couple of queries!! Which explains why each one was asking for the
same
information.

I removed the spaces and everything works as it should.

Thanks anyway. I appreciate your time.

Karen


:

I ment, check the properties of the fields in the report and not the report
itself, check if the fields bounded to the right fields in the query

:

Thank you for replying. I checked all the properties - the report properties
are set for the correct query. As mentioned earlier, the properties are also
set the same (e.g. currency). Any other suggestions?

Thanks Again.
Karen

:

It could be that you bounded the fields in the Report to the wrong names that
doesn't apear in the query.
Go through the fields and see if they all bounded to fields that apear in
the query.
On each field you can press on the ControlSource Property and see the list
of the fields, and you can see if you have a match

:

Hi Everyone.

I set up a report based on a query, where the user is prompted to enter
the start date and end date, which works great. However, why would some
of my other fields also prompt users to enter criteria? I set no criteria for
any other fields.

After user enters the date range, the report is asking for a [CostPerFoot]
parameter. I've checked the query parameters on the [CostPerFoot] and it's
set to
currency (in the report, query and table).

If I run the query only, it runs perfectly. Why is the [CostPerFoot]
parameter
showing up for the report??

Thanks for your help!

Karen