Form/subform connection works in Access 2003 but not in Access 2010 (both 32-bit)

[rimesparse]

I have a database with a form on top of the view/screen with static information for people and a subform below where I keep track of the projects done by those people (name of project, type of project, due date, etc.).

In Access 2003, even right now the database works perfectly fine. I see the person on top and their project history in the subform below.

In Access 2010, the form and subform aren't working correctly together. When I open the form, a pop-up prompt asks me to "Enter Parameter Value" for one of the fields in the form. The value it's asking for is unique to each of the records in the database. If I just click either "OK" or "Cancel" to the prompt, it then opens the form but all the data in subform is absent. The top form information looks fine, though.

Any idea what would have changed in Access 2003 vs. 2010 to break this? I have the database on a shared drive, so to be able to use it currently I have to open it on an old laptop that's still running Access 2003. (My regular computer has Access 2010.)

Many thanks for any advice.

Best,

PaulO

[RuralGuy]

Try and reselect the Control Value for that control and see if the problem goes away.

[rimesparse]

Try and reselect the Control Value for that control and see if the problem goes away.

OK, reselected the control source for that field (it's just a text field), but it's still having the same problem.

I did reconnect the form and subform using query builder and now records ARE appearing in the subform. But they are ALL the records in the subform for every person; i.e., it's not filtering them out per-person so I can see in the subform only what that one person has done.

Will keep tinkering, but any further ideas are welcome.

[RuralGuy]

Prompting for a parameter indicates something is probably misspelled.

[rimesparse]

Prompting for a parameter indicates something is probably misspelled.

I guess I just don't understand why it works in 2003 and not in 2010. If something were misspelled, how would it be working in Access 2003 like it is?

[RuralGuy]

Does it still ask for the parameter?

[RuralGuy]

I should remind you that *every* version of any software (especially Access) can be pickier on certain issues. They correct some known issues and then add a few issues that were not there before. I suspect you have had an issue since 2003 and it is just getting caught with 2010. Once we figure out what it is, we will see.