Enter parameter value prompt in ACCESS 2007 Report but not in 2003.
I have a strange behaviour that wasn't occuring a week ago. I have a database with a report that now gives me an "Enter Parameter Value" prompt for the field "ID1" which is the primary key that the query for the report is based on. The exact same database doesn't have this prompt on another machine that is running ACCESS 2003, but does have the same issue on another machine with ACCESS 2007. I actually copied the file to the other computer to make sure they were the same.
The second page of the report is linked as a child to the main form using ID1 from the main form and ID4 from the child.
Any ideas why this is happening in 2007 and not in 2003, and how can I make it stop?
Any ideas why this would change and what is causing it?
Thanks,
Pat
This may not be a cause, but I recently loaded Virtual studio 2005 on the two machines where the problem is happening.
The second page of the report is linked as a child to the main form using ID1 from the main form and ID4 from the child.
Any ideas why this is happening in 2007 and not in 2003, and how can I make it stop?
Any ideas why this would change and what is causing it?
Thanks,
Pat
This may not be a cause, but I recently loaded Virtual studio 2005 on the two machines where the problem is happening.
Jeffrey Coachman
Try using the same name for the both linking Fields.
ASKER
Sorry, I don't understand.
ASKER
Are you saying that I should change the name of the ID4 field on the child to ID1? If so, I just tried this. I changed the field name to ID1 in the child report page. It didn't work, but why would ID4 work in 2003, and not in 2007, as well as why would it work last week but not this week?
By the way, the child report page is based on a query of two tables that are linked on ID3 and ID4. Both of these are Primary keys.
Pat
By the way, the child report page is based on a query of two tables that are linked on ID3 and ID4. Both of these are Primary keys.
Pat
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks,
I really appreciate the examples you provided of ways this can happen. I deleted the existing queries and rebuilt them. You reminded me that if I delete or add a field, the queries get messed up unless you reconstruct them. I don't think I changed any field names, but the query rebuild was a good idea.
Just rebuilding the querywasn't enough however, I had to re-select them by getting into design view for the report, then select the data tab and reselect the query, and save. Everythibng worked fine,
Just doing that wasn't enough however, because when I closed the database and reopened, everything was lost. I had to redo it and then recompile. Now it is all locked in.
You help has saved me a lot of agony.
Thanks,
Pat
I really appreciate the examples you provided of ways this can happen. I deleted the existing queries and rebuilt them. You reminded me that if I delete or add a field, the queries get messed up unless you reconstruct them. I don't think I changed any field names, but the query rebuild was a good idea.
Just rebuilding the querywasn't enough however, I had to re-select them by getting into design view for the report, then select the data tab and reselect the query, and save. Everythibng worked fine,
Just doing that wasn't enough however, because when I closed the database and reopened, everything was lost. I had to redo it and then recompile. Now it is all locked in.
You help has saved me a lot of agony.
Thanks,
Pat
ASKER
Thanks.
OK great,
I am glad I helped.
;-)
Jeff
I am glad I helped.
;-)
Jeff