Prompting for unexpected parameter

[stormin_norm]

I'm scratchin' my head. Why access can get so PICKY!

I've built a report and it runs good.
I created a sub report and it runs perfect stand-alone.

I add the sub-report to the report, and now I'm prompted for a parameter which I never defined.

The prompt is for a parameter named "Student"

The Link Master Field contains Student.StudentID and thats about the only reference with "Student". So I figure I'll change the reports underlying query.

I change the query bound to the report to:
"Select Student.StudentID AS StudentStudentID, ...."

Change the filter on the report to StudentStudentID=3710
Change the Link to the new name StudentStudentID

And now it works, I no longer get prompted.

So WHY the heck did I have to change the underlying query column header to avoid this. My only guess is the FILTER. But then WHY does it run standalone and not when linked? STRANGE.

At least it works now. I'm wasting time with this flippant behavior. Will access truly survive?

-signed
'ripped by reports'

 

[stormin_norm]

Yes, I did recreate the links, actually numerous times.

I noticed when I wanted to check the links, as soon as I clicked on the down arrow, I received a warning message (more like a hand slap vs. yellow triangle) informing me about ensuring the links are defined. Which they were. So I simply selected the fields, hit okay. And noticed it happened again.

I'm not sure why. But modifying the query with a new name fixed the problem. I dare not recreate the report, it was a pain in the neck to align the subreports

Maybe I'll try to recreate a simple test version and attempt to duplicate the problem.

Thanks for the tips Pat! I appreciate all your posts to all my strange happenings

stormin' norm