Trace an Unexpected Access Parameter Prompt to Its Unresolved Name
An Access prompt asking for a start date may be an intentional part of a report. A new prompt showing something like TotalUntis after a field was renamed is a different clue. Establish whether the object was designed to ask the question before typing a value merely to make the dialog disappear.
Record the exact prompt text and the table, query, form or report being opened. Cancel the unexpected prompt. Preserve a database copy before design changes, and work with the database owner if the file is maintained by someone else.
Inspect the expression that names the missing item
Access can show Enter Parameter Value when it cannot interpret an identifier or expression. For a query, open Design View and inspect the Field and Criteria rows for the displayed name. For a report, use Design View and F4 to show the Property Sheet; inspect a data control's Control Source. A green triangle on a control is a useful clue that its expression cannot be evaluated.
In a fictional example, the table field might be TotalUnits while the report control still refers to TotalUntis. Compare the actual names and the intended source before changing the expression. A similar spelling is evidence to investigate, not proof that two fields mean the same thing.
If the report control appears correct, inspect the query supplying its data and trace the named expression there. Keep a brief record of the reference you changed so the correction can be reviewed. Do not create a new field with the misspelled name simply to satisfy the prompt.
Verify both the prompt and the result
Reopen the affected object in the working copy. Confirm that the unwanted question has gone, then inspect the value for a known record. Removing the dialog is only half the test: an expression can refer to an existing but incorrect field without raising that same prompt.
Also check another object that uses the corrected query or field. Retain any intentional parameter questions, and test them with a meaningful sample value. Document whether the fix corrected a spelling, a renamed field or a changed data source so the next maintainer can understand why the reference was updated.