Hi Melissa,
To recap so far, your form uses a query as it's recordset, and the query
runs fine, without producing the parameter prompt. Is this correct?
I've had success in the past using the method Karl Dewey mentioned, although
I wouldn't limit the database documentation to just the form and the
query--I'd simply document the entire database. Don't close the resulting
report until you have first exported it as a rich text file. Then search the
resulting document for the exact text that you are seeing in the prompt. You
could have an error in a macro, or in VBA code, that is tied to an event on
your form. It doesn't take that much extra time to just run the documentor on
the entire database, with everything selected.
An alternate method that I've used in particularly tricky cases is to start
by making a copy of the form. Then delete one control at a time, testing the
form each time. If there are lots of controls on your form, then use the
lasso technique in form design view to delete small groups of controls,
testing the form each time you delete a group of controls. If you find that
the problem goes away after deleting a particular group of controls, then
start over with a fresh copy of your form, repeating this test by deleting
one control at a time from the indicated group of controls.
Does the form include a subform? If so, try:
1.) Opening the subform by itself. Does it open without an error?
2.) Removing the subform from form design view of the parent form. If the
problem disappears after the second step, then you likely have an invalid
Link Master Field or Link Child Field.
Does the form include a class module (ie. is the Has Module property set to
Yes)? If so, try setting this property to No, and save the form, to delete
all VBA code behind the form. Does the error still occur after doing this?
Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________